Open Bug 1151336 Opened 10 years ago Updated 1 year ago

Figure out consequences for Sync clientID and local/remote history of backup/restore across devices

Categories

(Firefox for iOS :: Sync, defect, P3)

All
iOS
defect

Tracking

()

Tracking Status
fxios 10.0 ---

People

(Reporter: rnewman, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [MobileCore])

As I understand it, you can make a backup in iTunes and restore it to a second device. This will give you two devices that both think they own their client ID. We might need to somehow hash a device ID, exclude the client ID from backups, or some other solution to make this better. It's worth noting that sometimes this is desirable -- e.g., when replacing a device. Oh, for proper device management. There might be similar consequences for FxA certs and issued tokens.
Apple has made some provision for these situations that I intend to use for Account storage (although I'm not sure we do yet). See [1]. Specifically, Account stuff (email, uid, service endpoints) will be kSecAttrAccessibleAlways and State stuff (session tokens, oauth tokens, certificates, etc) will be kSecAttrAccessibleAlwaysThisDeviceOnly. (I see no reason to have to unlock the device first, etc.) [1] https://developer.apple.com/library/ios/documentation/Security/Reference/keychainservices/#//apple_ref/doc/constant_group/Keychain_Item_Accessibility_Constants
Depends on: 1182323
I just restored a phone backup to a new iPad. Firefox appeared. As expected, it's not signed in to sync. But it had my open tabs and my history. That means that: * The clients and commands tables are cloned from my phone. * Potentially the client ID is the same. * History local/remote bit is wrong. * If we add source device to history (Bug 1302797), it'll be wrong, too.
Blocks: 1302797
OS: iOS 8 → iOS
Summary: Figure out consequences for Sync clientID of backup/restore across devices → Figure out consequences for Sync clientID and local/remote history of backup/restore across devices
Tracking nom to think about this in the context of overall sync reliability. Firefox has been out for long enough now that users will be upgrading and buying second devices, and multiple devices is the value prop for Sync.
tracking-fxios: --- → ?
Priority: -- → P3
Whiteboard: [good-first-bug][lang=swift]
Whiteboard: [good-first-bug][lang=swift]
Blocks: 1343063
Whiteboard: [MobileCore]
Rank: 3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.