User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.39 Safari/537.36 Steps to reproduce: I opened Firefox Nightly (64 bit, 57 Branch) on Windows and I sent a tab to Firefox Nightly (57 Branch) on my Nougat (7.1.1) device. Actual results: Nothing, I have to wait until Firefox Sync start syncing following its default interval to see the notification of the sent tab. Expected results: The notification of the sent tab should arrive after some seconds, as it happen when I send the tab to Firefox for Android (55 Branch), because sending the tab should push the sync to happen.

I wonder if there's a problem registering a correct push_endpoint for your device. Can you try logging out of sync and logging back in? Renaming your android device to something unique in sync prefs will help distinguish it from the "old" version of it when you'll be looking for it on desktop. From your logs you appear to have both release and nightly installed. Are they both logged into the same account? Bug 1359279 might also be relevant here.

Can you also confirm you have a Google Account associated with that phone?

(In reply to :Grisha Kruglov from comment #1) > Can you try logging out of sync and logging back in? > > From your logs you appear to have both release and nightly installed. Are > they both logged into the same account? I logged out and logged back in and the problem persists. Yes, I had both release and nightly, but they were not synced to the same account when I noticed the problem, I logged in with the same account after noticing it to make a try. I also tried disconnecting and unistalling the release version, but it still does not work. (In reply to Edouard Oger [:eoger] from comment #2) > Can you also confirm you have a Google Account associated with that phone? Yes, I have it.

It's possible that this is a manifestation of Bug 1359279. I'd love to see the push endpoint your device has - that will let us figure out what's going on. You can also run the necessary test yourself. In the browser itself, you should be able to navigate to: file:///data/data/org.mozilla.fennec_aurora/GeckoPushState.json - on Nightly file:///data/data/org.mozilla.firefox/GeckoPushState.json - on release You should see a long string in there. Try to copy/paste it into an email to yourself or get it off the device in some other way. In that string, look for 'webpushEndpoint' url. If you can, try sending a POST request to it. If you run linux at all, you can do it in your terminal: curl -X POST https://updates.push.services.mozilla.com/wpush/v1/blahblahblah Alternatively, just paste the URL into https://www.hurl.it/ - select POST as request type. If you do have a valid endpoint, doing this will get your nightly to sync. You should also see logcat messages such as 08-10 20:42:20.493 8781 10645 D GeckoPushGCM: Message received. Processing on background thread. 08-10 20:42:20.493 8781 8811 I GeckoPushService: Google Play Services GCM message received; delivering. 08-10 20:42:20.493 8781 8811 I GeckoPushService: Message directed to service: fxa 08-10 20:42:20.493 8781 8811 D Telemetry: SendUIEvent: event = action.1 method = service timestamp = 34115889 extras = dom-push-api 08-10 20:42:20.493 8781 8811 I GeckoPushService: Delivering dom/push message to decode to Gecko! 08-10 20:42:20.494 8781 8813 I GeckoFxAccountsPush: FxAccountsPush _decodePushMessage 08-10 20:42:20.498 8781 8811 I GeckoPushService: Handling event: FxAccountsPush:ReceivedPushMessageToDecode:Response 08-10 20:42:20.498 8781 8811 I FxAccountPush: Handling FxA Push Message 08-10 20:42:20.499 8781 8811 I FxAccountPush: Received 'accountVerified' push event, requesting immediate sync If your endpoint isn't valid, you should see an error message after you POST - either in your console or on https://www.hurl.it You might see something like the following: {"code": 404,"errno": 102,"error": "Not Found","more_info": "http://autopush.readthedocs.io/en/latest/http.html#error-codes","message": "Request did not validate invalid token"} ... or what Bug 1359279 has in the first comment. If you're running into problems but are able to get at the file:///data/data/org.mozilla.fennec_aurora/GeckoPushState.json file, consider emailing it to me directly and I can run the tests (grisha@mozilla.com).

(In reply to :Grisha Kruglov from comment #4) > In that string, look for 'webpushEndpoint' url. Well, this is curious. In the release string there are an "autopushEndpoint" part and the "webpushEndpoint" one, while in the Nightly string there is only the "autopushEndpoint" part.

That means your nightly doesn't have a "push subscription", as we call it - which is what we'd use to actually send you a push message when you're sending a tab. Going to dig tomorrow into why that could be the case. Did you try POSTing to the webpushEndpoint that you did find, for the release version? Does _that_ not work as well? What do you see when you POST?

(In reply to :Grisha Kruglov from comment #6) > Did you try POSTing to the webpushEndpoint that you did find, for the > release version? Does _that_ not work as well? What do you see when you POST? POSTing to release works, I see it syncing when I execute the command, but the command succeeds without any logcat message.

Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Contact :susheel if you think this bug should be re-opened