VPN app "Create password" link not loading for users with Google/Apple accounts

[data-sync-user]

Important details:

• Page refresh fixes the issue and the user can successfully log into the account;

Version/build found in:

• 2.22.0 (2.202404222253) ;

Reproducible on:

• desktop;

Prerequisites:

• Have an account (Google/Apple or non Google/Apple) without a password set;
• Have the Mozilla VPN client installed;

Steps to reproduce:

1. Sign in using the account from prerequisites;
2. In the “Create a password” screen click the “Create password” link;
3. Observe the behavior;

Expected result:

• The user is taken to the Create password screen, opened in the preferred browser.

Actual result:

• The preferred browser opens up but the page is in a continuous loading state.

Notes:

• The workaround for this is to be logged into the FxA account with the same Google/Apple account;

┆Issue is synchronized with this Jira Bug
┆Reporter: Luminita Buruian

[data-sync-user]

➤ Santiago Andrigo commented:

Marking as high as this is a core user journey. It might be that we need to change the link target, if FxA can’t handle a direct link to “create password” when the user is not logged in (or FxA can fix that situation).

[data-sync-user]

➤ Lesley Norton commented:

Luminita Buruian Am I understanding correctly that this only happens when the user is not signed into FxA in their browser?

I can reproduce this by being 1.) signing out of my stage Fxa , 2.) attempting to open https://accounts.stage.mozaws.net/settings ( https://accounts.stage.mozaws.net/settings ) or https://accounts.stage.mozaws.net/settings/create_password ( https://accounts.stage.mozaws.net/settings/create_password ). I cannot reproduce this on Fxa Prod though or when logged into Fxa.

cc Benjamin Bangert do we think this is some quirk of Fxa Stage or maybe a change that hasn’t made its way to Prod yet?

Santiago Andrigo a bandaid could be for us to link to the accounts sign in page.

[data-sync-user]

➤ Santiago Andrigo commented:

This will be tracked by FxA as it's a bug on an FxA surface. Seemingly, it only affects Staging at this point, but we would want to make sure this bug doesn't propagate to Production. Lesley talking to Ben about it.

[data-sync-user]

➤ Wil Clouser commented:

Tracking @ https://mozilla-hub.atlassian.net/browse/FXA-9541 ( https://mozilla-hub.atlassian.net/browse/FXA-9541|smart-link )