iOS version of Bug 1356581. Bug 1354935 was caused by an apparently otherwise well-formed history record -- valid HMAC, decrypted correctly, had an ID -- having a payload that was JSON "null". We assume that this record came from desktop, given the users who know of who were affected. Those aren't Nightly users. It's not impossible that node reassignment is causing users to see their own records, though, so here's a bug for iOS. Let's investigate to make sure iOS doesn't create records with a null payload. Given a switch to SwiftyJSON, we should audit the places where we do checks -- SwiftyJSON requires explicit checks for `NSNull` and otherwise might have altered behavior.
We fixed this to my satisfaction.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.