2055471 - [Experiment] The VPN remains in a connecting state, if taping on the "Get started" button of the VPN Onboarding, while Firefox is already logged to an FxA account

Status: RESOLVED DUPLICATE of bug 2054812

(Firefox for Android :: Privacy, defect)

Description

[Cosmin Muntean [:cmuntean], Ecosystem QA - PTO until 18 Sept - ping mcoman for any question]

Attachment: Record_2026-07-16-12-47-10 (1).mp4

[Notes]:

• The issue is NOT reproducible if Firefox is not logged to an FxA account before clicking the "Get started" button from the VPN Onboarding.
• I can also reproduce this with a new FxA account.
• I have downloaded Firefox RC 153 version from here.
• I have reproduced this on Open Plus 9 Pro with Android 14.
• The device has the language set to: English and the region set to the United States.

[Affected versions]:

• Firefox RC 153.0 (Build #2016172922), 3810496e857367d04cf4fa0c705df6995a48b860, GV: 153.0-20260715202819, AS: 153.0, OS: Android 14

[Affected Platforms]:

• Android 14

[Prerequisites]:

• Have a Firefox RC build that was installed at least 7 days ago.
• Have the nimbus-cli tool installed.
• Have adb (cli) installed on your device.
• Have the Android device connected to your PC.
• Have the Firefox RC (Fenix) browser v153 installed.
• Make sure that your Android device and Firefox browser meet the targeting criteria (language en, region US).
• Have the nimbus cli path added into the environment variable.

[Steps to reproduce]:

1. Make sure Firefox is not enrolled in the experiment.
2. Log in to a valid FxA account and close the Firefox browser.
3. Open the cmd/terminal window and run the nimbus-cli command to enroll in the rollout: nimbus-cli --app fenix --channel release enroll preview/vpn-android --branch treatment-a --preserve-targeting.
4. Make sure that the Onboarding is triggered.
5. Tap "Get started".
6. From the FxA page, tap the "Continue" button.
7. Observe the VPN panel.

[Expected result]:

• VPN is successfully connected.

[Actual result]:

• A "Couldn't connect to VPN. Try again in a few minutes." message is displayed and VPN remains in a "Connecting..." state, until the browser is restarted.

[Additional Notes]:

• Attached is a screen recording of the issue.

Comment 1

[Mike a [:mavduevskiy]]

There was a similar bug filled a few days before that, and after testing & logging it was confirmed to be the same technical issue, despite STR's being slightly different. But both STRs are valid ways to reproduce the bug, thank you!