Closed Bug 618945 Opened 14 years ago Closed 5 years ago

Sync update message not displayed on the device

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(fennec-)

RESOLVED WONTFIX
Tracking Status
fennec - ---

People

(Reporter: ashah, Unassigned)

Details

1.
Environment:
Desktop: FF 3.5.15/FF 3.6.12/FF 4.0b7 + Sync 1.6
Device: 4.0b2 (comes with Sync 1.5 installed)

Steps to perform:
1.Install FF 3.5.15 or FF 3.6.12 or FF 4.0b7 with Sync 1.6
2. Configure a sync account and sync.
3. On device, install Fennec 4.0b2. Configure with the account from step 2. Sync

Expected:
"Please update to the latest version" message should be displayed on device.

Actual:
"Wrong sync key".

Note:
The results are as expected for the following scenario (which is more close to a real case scenario)

1.Install FF 3.5.15 or FF 3.6.12 or FF 4.0b7 with Sync 1.5
2. Configure a sync account and sync.
3. On device, install Fennec 4.0b2. Configure with the account from step 2. Sync
4. Update sync extension to 1.6 on desktop. Sync
5. Sync with the device

Results: FF 4.0b2 is not compatible with the latest version of Firefox Sync. Please update to the latest version.
This is a Fennec UI bug, not a Firefox UI bug. The Fennec UI should check for Weave.Status.sync == Weave.VERSION_OUT_OF_DATE.
Component: Firefox Sync: UI → General
OS: Mac OS X → All
Product: Mozilla Services → Fennec
QA Contact: sync-ui → general
Hardware: x86 → All
Version: unspecified → Trunk
We do check for that in a "weave:service:sync:error":
http://mxr.mozilla.org/mobile-browser/source/chrome/content/sync.js#418

Is there a different topic we should use?
flagging for blocking.  error messages are incorrect and unhelpful to how the user can fix the problem.
tracking-fennec: --- → ?
If this still happens in Fennec 4 Beta 3 (or a nightly), let's fix.
tracking-fennec: ? → 2.0-
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.