Closed
Bug 616312
Opened 15 years ago
Closed 15 years ago
Cannot sync error after upgrade (ciphertext = nil exception)
Categories
(Cloud Services Graveyard :: Firefox Home, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tchung, Assigned: st3fan)
Details
Attachments
(1 file)
|
98.60 KB,
image/png
|
Details |
I keep hitting this error after i updated to the 1.1 beta 5 on my iphone 4. -[__NSCFDictionary setObject:forKey. Was not connected prior, nor was i trying to sync to the 1.6 extension or firefox build.
* See screenshot
REpro:
1) installed FF Home 1.1b5 OTA on iphone 4, iOS 4.1, on 3G network
2) launch home
3) click i have an account
4) when jpake loads, just let it sit for awhile
5) crypto error popup
Expected:
- not sure how i got it, but no error thrown
Acutal:
- -[__NSCFDictionary setObject:forKey error
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → stefan
| Assignee | ||
Comment 1•15 years ago
|
||
Tony, did you have Home 1.0.4 installed on this device before? Did the 1.1b5 install replace that version that you already had?
| Assignee | ||
Updated•15 years ago
|
Assignee: stefan → nobody
Component: General → Firefox Home
Product: Fennec → Mozilla Services
QA Contact: general → firefox-home
Version: Trunk → unspecified
| Assignee | ||
Updated•15 years ago
|
OS: Android → iOS 4
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → stefan
| Assignee | ||
Updated•15 years ago
|
Summary: Crypto script error on jpake screen → Cannot sync error after upgrade (ciphertext = nil exception)
| Assignee | ||
Comment 2•15 years ago
|
||
Fixed for 1.1b6
This happens if we upgraded to new crypto but we are still logged in with the 'old' account. In that case we do not have new style crypto/hmac keys, which means that we also cannot encrypt and upload a new client record.
Changeset: http://hg.mozilla.org/services/fx-home/rev/62cb18c43ab8
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•