1385535 - after logging in & email verifying for syncing. Firefox does not sync & email verification button still appear & synchronization status is 'never'. nothing at all was synced.

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: Firefox Accounts, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (Android 5.1.1; Mobile; rv:55.0) Gecko/55.0 Firefox/55.0
Build ID: 20170613141526

Steps to reproduce:

syncing Firefox data


Actual results:

after logging in & email verifying for syncing. Firefox does not sync & email verification button still appear & synchronization status is 'never'. nothing at all was synced. 


Expected results:

dismiss email verification button & synchronize all bookmark history password & tabs.

Comment 1

[Nevin Chen(Not active on Bugzilla)]

I had this before.
I need to restart the app several times. Sometimes I just login again.
Hi Grisha
Could you please advise? Thanks!

Comment 2

[:Grisha Kruglov]

After a login is verifying, app _should_ receive a push message which will prompt a sync. IIRC that landed fairly recently, perhaps it wasn't in 55, but it is in 57.

Once a sync is triggered, the error banner should disappear. In any case, once a login has been verified, you _should_ be able to sync by tapping "Sync now".

Nevin, what happens after you verify a login and tap Sync Now? Can you reproduce this state nightly? Can you watch the logcat output while you click on the verification link, and observe if you will see a GCM push message come in?

Comment 3

[Kenneth P]

I'm coming up with just about the same symptoms. I follow the email verification flow for desktop and then mobile, but it appears on the server side my account is not actually completing verification, with this error in the desktop (Windows) sync log:

1505871402477	Services.Common.RESTRequest	TRACE	POST body: {"code":400,"errno":104,"error":"Bad Request","message":"Unverified account","info":"https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#response-format"}

This is the exact flow I followed:

1. GA (55?) installed with sync working on both desktop and android
2. Upgraded GA to Beta (57) on desktop, no uninstall
3. Installed android beta (57)
4. Uninstalled android GA (55)
5. Tried to set up sync on android-- verification email said it verified, and sync seems to fail for that reason.

I tried re-sending email from desktop as well, but everything still shows up as unverified even though the verification link appears successful. The only push notification I have received throughout the flow is the one saying "Sync is not connected: Tap to sign in as", nothing special upon using a verification link.

Are there any logs I can pull from the android side maybe that can help? Or maybe I should try creating a new sync account (but I can't seem to deactivate my current since the verification flow blocks managing it)?

Comment 4

[Ryan Kelly [:rfkelly]]

Kenneth, to clarify, is you account staying unverified on both desktop and android, or only on android?  That's very odd and we should follow up in a separate bug.  Is the email on your account the same as the one you're using here for bugzilla?

Comment 5

[Kenneth P]

(In reply to Ryan Kelly [:rfkelly] from comment #4)
> Kenneth, to clarify, is you account staying unverified on both desktop and
> android, or only on android?  That's very odd and we should follow up in a
> separate bug.  Is the email on your account the same as the one you're using
> here for bugzilla?

I think I got this working by disconnecting sync on the desktop side and setting things up fresh, or something like that. It's been working since, so there probably isn't anything left to investigate on my account, unfortunately. Thanks for the reply!

Comment 6

[Nevin Chen(Not active on Bugzilla)]

I can't reproduce this now.
I think we can close this bug?

Comment 7

[Stefan Deiac]

 (In reply to Nevin Chen(Not active on Bugzilla) from comment #6)
> I can't reproduce this now.
> I think we can close this bug?

Given the comment I will close the issue. If the issue it's reaper please reopen it.