Please report any other irregularities here.
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141106120505 Steps to reproduce: 1. Login the same Firefox account in two Android devices. 2. Settings -> Accounts -> Firefox account -> "Sync Now". 3. Continuously tap on the "Sync Now" button on both devices simultaneously. Actual results: After a particular time, Check the Tab sync list in one of the devices, Duplicate entries are found. Login the same Firefox account in Desktop Firefox Browser, Duplicate entries are not present. Expected results: No Duplicate entries should found.
Component: General → Android Sync
Product: Firefox for Android → Android Background Services
Thanks for the report! Is it possible that you could screenshot the Synced Tabs panel to show the issue? Could you then restart Firefox and see if the list of Synced Tabs is still the same, with duplicates? I want to know if this is a display issue (we get confused about the number of tabs in the database) or a database issue (we're really getting the wrong set of tabs from Sync). Thanks!
There are duplicate entries in the Database itself. We have closed (Force stop) the Firefox browser & opened again, still it shows the duplicate entries. I think it is not an UI issue. Please check it further. As per the security reason of the company i couldn't upload the screenshot of the issue. Sorry.
Can you provide an adb log? adb shell setprop log.tag.FennecTabsSession VERBOSE adb logcat -v time > log.txt Ctrl-C after you've reproduced the problem, then upload log.txt to this bug.
Sidenote: this is theoretically possible if two syncs can run concurrently on the device, but Android is supposed to prevent that from happening.
Not sure if there have been other reports about this in the past few years (very likely I'm not seeing them). But as is, this bug is inactionable. Feel free to re-open if this _is_ being actively encountered.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Priority: -- → P3
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.