1059310 - Add-ons are updated while sync'ed between machines

Status: RESOLVED WONTFIX

(Firefox :: Sync, defect)

Description

[Camelia Badau [:cbadau], Desktop Test Engineering]

Attachment: issue sync.png

Reproducible on Firefox ESR 24.8.0 (buildID: 20140825140210)
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0

Prerequisites: You have two machines (clients) setup with the same Sync account and they are both signed in.

Steps to reproduce: 
1. On your first machine, we'll call this client A, install an addon with an old version (e.g: Firebug 1.12.8.) from https://addons.mozilla.org/.
2. Click Tools > Sync Now.
3. Go to your second machine, we'll call this client B. Click Tools > Sync Now.

Actual results: The addon installed on client A is now on client B, but with the most recent version for this addon and is disabled - "incompatible for Firefox 24.8.0"(e.g: Firebug 2.0.3). See screenshot "issue sync.png". 

Expected results: The addon installed on client A is now on client B (with the same version and is enabled). 

Note: This issue is reproducible also on Windows 8 32bit, Ubuntu 14.04 32 bit and Mac OS X 10.7.

Comment 1

[Kamil Jozwiak [:kjozwiak]]

Camelia, is this a new regression that's only occurring in the current 24.8 ESR branch or does this also happen in any of the other 24.x branches? (for example, ESR 24.7)

Could you please see if you can reproduce this in m-c and in the current ESR 32 build? I want to make sure this isn't a general sync issue that's happening on all other branches.

Comment 2

[Camelia Badau [:cbadau], Desktop Test Engineering]

This issue also reproduces on: 
- Firefox 24.0, ESR 24.5.0, ESR 24.6.0, ESR 24.7.0 - same actual results like in comment #0. 
- latest Nightly 34.0a1 (buildID: 20140827030202), latest Aurora 33.0a2(buildID: 20140827004002), Firefox 32 RC (buildID: 20140825202822) - actual results: the addon installed on client A is now on client B, but with the most recent version for this addon(e.g: Firebug 2.0.3) and is enabled (compatible) -> the difference here is that the updated addon (displayed on client B) is compatible with Firefox and is enabled.

Comment 3

[(mostly gone) XtC4UaLL [:xtc4uall]]

See Bug 726284 Comment 5 for reasoning why it is as it is.

Comment 4

[Mark Hammond [:markh] [:mhammond]]

In addition to the reasoning in bug 726284 Comment 5, we simply reply on addons.mozilla.org to do the right thing - we never ask AMO for a specific version, just for the best version. This should work as expected so long as the addon makes a correct version available.