Closed Bug 606046 Opened 14 years ago Closed 12 years ago

cannot sync: Incorrect Sync Key

Categories

(Cloud Services Graveyard :: Firefox Home, defect)

Other
iOS 4
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jbecerra, Unassigned)

Details

Today I opened the application and I got that error message. The only difference between yesterday (when it worked) and today is that I disabled wi-fi. Also, when I enter my credentials, it starts sync'ing tabs and bookmarks and it chokes at some point and gives me that error again.
Hardware: x86 → Other
Is this with 1.0.3 ?
This is version 1.0.3 of Fx Home.
Is this reproducible? If so, would you mind writing down the steps?
Yesterday it happened reliably, today I cannot reproduce the problem. The steps were: 1. Sign in and sync while using wi-fi 2. Turn off wifi 3. Re-open Fx Home Expected: I'd be able to see my tabs or whatever. Actual: Error message as in the summary Entering the credentials would initiate the synchronization, but it would not complete it and it would complain with the error above. If I clicked on the tabs icon before the error came up, I would be able to see them. If it let the synchronization try to finish I would get the error message. Note: Before yesterday I had not used the app in several days.
Juan, can you retest this on 1.0.4 when it finally lands in the App Store? I'll also try this on my 1.0.4 beta builds
Flags: blocking-fx-home1.1?
Flags: blocking-fx-home1.1?
The Firefox Home project has been retired, and Mozilla will no longer invest in future work on this project [1]. All bugs related to Firefox Home are being mass resolved. For those interested in continuing work on this app, the source code for Firefox Home is available on Github [2]. [1] http://blog.mozilla.org/services/2012/08/31/retiring-firefox-home/ [2] https://github.com/mozilla-services/ios-sync-client
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.