Duplicate notifications received if sent tabs are to multiple synced devices

NEW
Unassigned

Status

()

P5
normal
a year ago
a month ago

People

(Reporter: u549602, Unassigned)

Tracking

57 Branch
ARM
Android
Points:
---

Firefox Tracking Flags

(firefox57 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8894862 [details]
receiving Bulk notifications.txt

Device: Samsung Galaxy Tab S3 Android 7.0
Build : 57.0a1

STR:

1. Have multiple devices synced with the same FxA
2. Send all multiple tabs from desktop

Expected: 
A notification with the tab information is received at each sent tab

Actual:

A bulk of sent tabs is received each time a tab is sent 

For further details please check: https://www.youtube.com/watch?v=IzVQw_VKuYI&feature=youtu.be

Also a logcat attached, too big for pastebin.
Component: General → Android Sync

Comment 1

8 months ago
The logcat shows:

08-08 16:04:46.897: W/FxAccounts(23809): firefox_beta :: SSResourceDelegate :: HTTP request failed.
08-08 16:04:46.901: W/FxAccounts(23809): firefox_beta :: SSResourceDelegate :: HTTP response body: 0
08-08 16:04:46.905: W/FxAccounts(23809): firefox_beta :: GlobalSession :: Aborting sync: Client upload failed.
08-08 16:04:46.905: W/FxAccounts(23809): <HTTPFailureException 412 :: (0)>
08-08 16:04:46.905: W/FxAccounts(23809): 	at org.mozilla.gecko.sync.stage.SyncClientsEngineStage$ClientUploadDelegate.handleRequestFailure(SyncClientsEngineStage.java:381)

Which I presume means that we fail to re-upload our commands with the already-processed commands removed, so re-process them next sync. No clue why there's a 412 here though - if it is happening reliably I doubt it really means another client always races to update the collection.
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
QA Contact: mihai.ninu
QA Contact: mihai.ninu → stefan.deiac
You need to log in before you can comment on or make changes to this bug.