Wrong error screen is displayed when the user has a subscription in use associated with another Fx account and clicks on "Already a subscriber?" button

[data-sync-user]

Important details: 

• Reproducing with 2.17.1 as well.

Affected versions:

• 2.18.0 (2.202310022206);

Tested Platforms:

• iOS;

Prerequisites:

• Have a Fx account with no subscription

• Have another Fx account with an active subscription for Mozilla VPN

• Have an Apple ID that is associated with the Fx account that has the active subscription for Mozilla VPN

• Have Mozilla VPN app installed and opened

Steps to reproduce:

1. Sign in with the account with no subscription.
2. On the IAP screen, click on “Already a subscriber?” button.

Expected result:

• An error message is displayed on the screen: "Another Mozilla Account has already subscribed using this Apple ID. Please sign out and try again or contact our support team for help." and a "Sign out" blue button.

Actual result:

• An error message is displayed on the screen: “Your subscription is linked to another Firefox Account. You may need to sign in with a different email address. Visit our help center to learn more about managing your subscription”, along with a “Get help” blue button with white label and a “Sign out” red button. 

Notes:

• See the attached screenshot;

┆Issue is synchronized with this Jira Bug ┆Reporter: Raluca Monica Ilban

[data-sync-user]

➤ Santiago Andrigo commented:

Peter Benvenuto do you have the Figma file for what we intended to show here?

Messaging wise, what we seem to expect is more clear to me than what we are showing, but it seems to me like we should flip the buttons at bottom so that the primary is to sign out and the secondary is to get help. Wdyt?

[data-sync-user]

➤ Peter Benvenuto commented:

Santiago Andrigo I think this is another one of those weird layout things again. I don’t think I worked on this screen, but it shouldn’t be laid out like this. This is definitely a bug and get help should never be a primary CTA.

[data-sync-user]

➤ Valentina Virlics commented:

This is currently still reproducing on iOS 16 while using Mozilla VPN 2.22.