1548332 - [Android Q] After configuring my Firefox Account, Sync says "Your account needs to be verified. Tap to resend verification email." (But there's never any email or option to send one.)

Status: RESOLVED DUPLICATE of bug 1537701

(Firefox for Android Graveyard :: Android Sync, defect, P1)

Description

[Daniel Holbert [:dholbert]]

STR:

1. Be running Android Q. (This only started happening to me on that version, and it happened on two separate phones [Pixel 3 and Pixel 2] when I upgraded them to Q and installed Nightly)

2. Install Firefox Nightly, and log in to your Firefox Account (e.g. by clicking through the prompt on the firstrun experience about Sync)

3. In Nightly Settings, tap "Firefox Account" at the top.

ACTUAL RESULTS:
There's a red box saying:

Your account needs to be verified. Tap to resend verification email.

There's never any verification email, though. (There was never one in the first place, and if I tap the box as suggested, it just takes me to an about:accounts page with info about my Firefox account and no obvious "send verification email" step)

EXPECTED RESULTS:
Sync should work.

In the time since I've hit this bug, I've been able to successfully configure Firefox Nightly on an earlier Android version ("Pie") with no mention of verification emails and no trouble. I suspect some piece of account configuration is failing, and Firefox Nightly's message about the confirmation email is an off-target attempt at self-diagnosis.

Comment 1

[Daniel Holbert [:dholbert]]

In case it's relevant, here's the snippet of logcat from just after I sign in to my Firefox Account -- note the "
cipherSuite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 is not supported` message which is bug 1537701.

(I'm not sure whether or not this entire bug is a dupe of bug 1537701 -- I filed it because nalexander thought my error message about verification emails might be a sign of something else broken.)

05-01 11:13:45.041 18664 18697 I GeckoFxAccounts: Created or updated Firefox Account.
05-01 11:13:45.055 18664 19570 I FxAccounts: fennec_aurora :: FxAccountSyncAdapter :: Syncing FxAccount account named like [e-mail] for authority org.mozilla.fennec_aurora.db.browser with instance org.mozilla.gecko.fxa.sync.FxAccountSyncAdapter@ccbb0d9.
05-01 11:13:45.056 18664 19570 I FxAccounts: fennec_aurora :: FxAccountSyncAdapter :: Account last synced at: -1
05-01 11:13:45.057 18664 19570 I FxAccounts: fennec_aurora :: FirefoxAccounts :: Sync options -- scheduling now: false
05-01 11:13:45.066 18664 19570 D GeckoLogger: Thread with tag and thread id acquiring lock: FxAccountSyncAdapter, 8152 ...
05-01 11:13:45.066 18664 19570 D GeckoLogger: Thread with tag and thread id acquiring lock: FxAccountSyncAdapter, 8152 ... ACQUIRED
05-01 11:13:45.103 18664 19589 I FxAccounts: fennec_aurora :: LoginStateMachineDelegate :: handleTransition: Log(java.io.IOException) to Engaged
05-01 11:13:45.103 18664 19589 I FxAccounts: fennec_aurora :: LoginStateMachineDelegate :: handleFinal: in Engaged
05-01 11:13:45.103 18664 19589 I FxAccounts: fennec_aurora :: AndroidFxAccount :: Moving account named like [e-mail] to state Engaged
05-01 11:13:45.119 18664 19589 I FxAccounts: fennec_aurora :: FxAccountNotificationManager :: State Engaged needs action; offering notification with title: Sync is not connected
05-01 11:13:45.121 18664 19589 I FxAccounts: fennec_aurora :: LoginStateMachineDelegate :: handleNotMarried: in Engaged
05-01 11:13:45.121 18664 19589 I FxAccounts: fennec_aurora :: FxAccountSchedulePolicy :: Scheduling periodic sync for 60.
05-01 11:13:45.121 18664 19589 W FxAccounts: fennec_aurora :: FxAccountSyncAdapter :: Cannot sync from state: Engaged
05-01 11:13:45.121 18664 19570 D GeckoLogger: Thread with tag and thread id releasing lock: FxAccountSyncAdapter, 8152 ...
05-01 11:13:45.121 18664 19570 D GeckoLogger: Thread with tag and thread id releasing lock: FxAccountSyncAdapter, 8152 ... RELEASED
05-01 11:13:45.122 18664 19570 I FxAccounts: fennec_aurora :: FxAccountSyncAdapter :: Syncing done.
05-01 11:13:45.127  1414  1834 W SyncManager: failed sync operation JobId=102003 ***/org.mozilla.fennec_aurora_fxaccount u0 [org.mozilla.fennec_aurora.db.browser] OTHER ExpectedIn=0s STANDBY-EXEMPTED(TOP) Reason=AutoSync, SyncResult: stats [ numIoExceptions: 1 numUpdates: 1]
05-01 11:13:45.129 18664 19589 I FxADeviceListUpdater: Beginning FxA device list update.
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: Error while getting the FxA device list.
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: java.io.IOException
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.execute(BaseResource.java:326)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.retryRequest(BaseResource.java:349)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.execute(BaseResource.java:330)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.go(BaseResource.java:373)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.get(BaseResource.java:379)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.background.fxa.FxAccountClient20.deviceList(FxAccountClient20.java:897)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.devices.FxAccountDeviceListUpdater.update(FxAccountDeviceListUpdater.java:121)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.devices.FxAccountDeviceListUpdater.updateAndMaybeRenewRegistration(FxAccountDeviceListUpdater.java:128)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.sync.FxAccountSyncAdapter.onSessionTokenStateReached(FxAccountSyncAdapter.java:495)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.sync.FxAccountSyncAdapter.access$300(FxAccountSyncAdapter.java:74)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.sync.FxAccountSyncAdapter$3.handleNotMarried(FxAccountSyncAdapter.java:668)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.authenticator.FxADefaultLoginStateMachineDelegate.handleFinal(FxADefaultLoginStateMachineDelegate.java:78)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.login.FxAccountLoginStateMachine$ExecuteDelegate.handleTransition(FxAccountLoginStateMachine.java:64)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.fxa.login.BaseRequestDelegate.handleError(BaseRequestDelegate.java:47)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.background.fxa.FxAccountClient20$1.run(FxAccountClient20.java:173)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at java.lang.Thread.run(Thread.java:919)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: Caused by: java.lang.IllegalArgumentException: cipherSuite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 is not supported.
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at com.android.org.conscrypt.NativeCrypto.checkEnabledCipherSuites(NativeCrypto.java:1122)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at com.android.org.conscrypt.SSLParametersImpl.setEnabledCipherSuites(SSLParametersImpl.java:225)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at com.android.org.conscrypt.ConscryptFileDescriptorSocket.setEnabledCipherSuites(ConscryptFileDescriptorSocket.java:731)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.conn.ssl.SSLSocketFactory.internalPrepareSocket(SSLSocketFactory.java:499)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:506)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:377)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:165)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:145)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:860)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at ch.boye.httpclientandroidlib.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	at org.mozilla.gecko.sync.net.BaseResource.execute(BaseResource.java:308)
05-01 11:13:45.134 18664 19589 E FxADeviceListUpdater: 	... 17 more

Comment 2

[Daniel Holbert [:dholbert]]

Attachment: screenshot of the error on Sync settings page

Comment 3

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #1)

(I'm not sure whether or not this entire bug is a dupe of bug 1537701 -- I filed it because nalexander thought my error message about verification emails might be a sign of something else broken.)

Even if the underlying problem here is a dupe of bug 1537701 [the cipher issue], there's arguably still a distinct bug in how we're self-diagnosing and surfacing the failure to the user here, and perhaps there's separate work to be done to address that.

Comment 4

[Daniel Holbert [:dholbert]]

Version: Firefox Nightly 68.0a1 (2019-05-01)

Comment 5

[Chris Peterson [:cpeterson]]

Adding [geckoview:fenix:m7] whiteboard tag because we should fix our Android Q bugs soon but they're not strictly Fenix MVP release blockers.

Comment 6

[Daniel Holbert [:dholbert]]

FWIW, this is no longer reproducible now that bug 1537701 has been fixed.

It'd still be nice to improve the error/warning messaging for this scenario to avoid sending the user on a bogus wild-goose-chase for nonexistent confirmation emails, though I'm not sure about the priority of that, given the existence of Fenix (and given that it's conceivable that this bogus-messaging failure-mode isn't reachable now that bug 1537701's been fixed).

Comment 7

[dmitry.myachin]

Same. Android Q, Firefox 67

Comment 8

[bdmorin]

I have this same issue, Android Q, unable to verify.

Comment 9

[Daniel Holbert [:dholbert]]

The underlying issue is already fixed in Firefox Nightly (and probably in Firefox Beta as well -- it was fixed via bug 1537701 which is included in version 68, which is currently on the beta channel)

If you're running into this and want a workaround, I'd suggest switching to Firefox Beta (or Nightly) for Android. Release will presumably be fixed when it updates to version 68, which should be mid-July.

Comment 10

[Eitan Adler]

I ran into this bug on Release. Tried Firefox Beta (as of today, I can't find a version number) and it was fixed.

Comment 11

[Eitan Adler]

found the version number: confirmed fix on 68.0b7

Comment 12

[Chris Peterson [:cpeterson]]

(In reply to Eitan Adler from comment #10)

I ran into this bug on Release. Tried Firefox Beta (as of today, I can't find a version number) and it was fixed.

Thanks for testing, Eitan! I think this bug was fixed in 68 by SSL bug 1537701.

Comment 13

[Daniel Holbert [:dholbert]]

(In reply to Chris Peterson [:cpeterson] from comment #12)

Thanks for testing, Eitan! I think this bug was fixed in 68 by SSL bug 1537701.

Yes, per comment 9. I'd left this open to track the fact that the UI is still broken when this sort of error surfaces, but I'm not sure how useful that is to track, so closing is fine, but we might as well dupe to bug 1537701 in that case.

Having said that: this actually just regressed today, when I updated from Android Q beta3 to beta4, so I think the APIs/ciphersuites in question may have changed again. So: I'm going to file a new bug on the resurfaced issue in Q beta4, and I'll mark this bug here as a dupe of bug 1537701.

Comment 14

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] (reduced availability until June 12) from comment #13)

So: I'm going to file a new bug on the resurfaced issue in Q beta4

I filed bug 1557203 as the new bug for this.