This ticket tracks adding a storage layer for Firefox Account profile information. I think it's worth just keeping JSON in the format provided by the profile server  around for at least a while, and perhaps adding a little API for accessing it in a type safe way. Right now that's just a URI to a profile image, I think. This API would be provided via an AndroidFxAccount on device and might handle downloading and caching the profile image for future use. At some point this might grow into a ContentProvider and a Sync adapter to maintain the data; or we might update the data in response to interactions with the web view at accounts.firefox.com. But for now, we can stay nice and simple.  https://github.com/mozilla/fxa-profile-server
We might want to expose this profile data through Accounts.jsm as well, for add-ons and home panels to take advantage of. Food for thought.
3 years ago
Whiteboard: [lang=java][good next bug]
Yeah, JSON and a little AndroidFxAccount sub-API for getting the profile information is enough for now. There's an impedance mismatch here: the Android account is a global object, while the Firefox Account profile (avatar, etc) should be tied to a specific Firefox profile. That is, the Account really belongs to the "default" profile. So we should be careful to store the profile JSON in a per-Firefox-profile location. The profile is available to AndroidFxAccount, so that should work out.
Summary: Store Firefox Account profile information → Store Firefox Account profile information using SyncAdapter and ContentProvider
Whiteboard: [lang=java][good next bug] → [lang=java]
Bulk edit: moving potentially relevant issues from disabled Android Background Services product to Firefox for Android. Removing priority to throw back to triage owners: please close these bugs if they're no longer relevant! Thanks!
Component: Firefox Accounts → Firefox Accounts
Product: Android Background Services → Firefox for Android
We almost certainly aren't going to touch this any time soon
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.