Email Aliases: Clicking "Get Started" opens a blank window


Description

The newly released Email Aliases feature is not working correctly during the initial setup.

When I open Settings → Autofill and passwords → Email Aliases and click “Get Started”, a blank modal/window appears and the setup process does not continue.

Steps to Reproduce

  1. Open Brave Browser.
  2. Go to Settings → Autofill and passwords → Email Aliases.
  3. Click “Get Started”.
  4. Observe the window/modal that appears.

Actual Result

A blank dark modal/window appears with no content or controls.

The Email Alias setup process cannot be completed from this screen.

Expected Result

Clicking “Get Started” should open the Brave Account sign-up/login flow and allow me to continue setting up Email Aliases.

Brave Version

Brave 1.94.117 (Official Build) (arm64)

Chromium: 152.0.7977.64

MacOS: Tahoe 26.5.2 (25F84)

Additional Information

This appears to affect the initial onboarding flow for the newly released Email Aliases feature.

Screenshot attached showing the blank modal after clicking “Get Started”.

The issue occurs before I am able to create or configure an Email Alias.

Thanks for reporting. Do you also see this if you try from a fresh profile? (Menu → More Tools → Add New Profile) Thanks for confirming!

Thanks for the reply. Yeah, it’s also happening in fresh new profile.

Can you submit an issue below under the Email Alias option? Could you also include any errors you see in your Console logs when attempting to click Get Started? To open Console, select (FN +F12).

Please also confirm you aren’t running any DNS or network tools that may be blocking aliases.

Thanks!

  1. Sorry, i can not see any “Email Alias” in category
  2. I attach my screen record. it seems that i can not access to brave://account/
  3. I have disconnected my VPN and using default dns

Hey there,
Could you try opening this URL in a new tab?
chrome://resources/brave/5d3bd3eeba554df6204a.module.wasm

Hi, this is what i get

Thanks, that’s helpful!
I’m on the same build as you, but my copy expects a different filename than yours, which is odd for identical builds.
Could you try this URL in a new tab and let me know what you get?

chrome://resources/brave/7a5f5af89536676139a4.module.wasm

Ahh i see. the new URL is worked

Sorry, one more thing. Could you run this in Terminal and paste what it outputs?

grep -ao "brave/\[0-9a-f\]\\{20\\}\\.module\\.wasm" "/Applications/Brave Browser.app/Contents/Frameworks/Brave Browser Framework.framework/Versions/Current/Brave Browser Framework"

no problem. i try to run it but returns nothing. is this command correct?

Sorry, looks like Discourse mangled the quoting on the way to you. Try this version instead:

grep -ao "brave/[0-9a-f]\{20\}\.module\.wasm" "/Applications/Brave Browser.app/Contents/Frameworks/Brave Browser Framework.framework/Versions/Current/Brave Browser Framework"

oh right, it return something now

Thanks for sticking with me on this!

I think I have a pretty good idea of what’s going on. Could you run this command for me so I can confirm?

file "/Applications/Brave Browser.app/Contents/Frameworks/Brave Browser Framework.framework/Versions/Current/Brave Browser Framework"

no problem, glad to help. This is the return

Thanks a lot! That settles it (I also confirmed it locally). I’ve filed https://github.com/brave/brave-browser/issues/58576 and should be back with a fix soon.

that’s a good news. thank you very much.

Hey there,

Thanks again for the help pinning this down.

The fix landed in Nightly on August 31 and is scheduled to reach the Release channel next week.

In the meantime, if you’d rather not wait, the platform-specific installers aren’t affected. Installing Brave-Browser-arm64.dmg (for Apple Silicon) instead of the universal installer will get Email Aliases working right away.

Hi, thanks a lot for your hard work.
I just updated my brave today to Brave 1.94.121 (Official Build) (arm64) and it works perfectly.

I am on a M4 Pro Macbook and still having this issues with the latest update.