Side-effect of calling /certificate/sign is creation of a placeholder fxa device record if one isn't already present. From rfkelly (): > * If we get a request to /certificate/sign, and > * That sessionToken does not have a device id associated with it, and > * There's no ?service= query parameter, or there's service=sync, then > * Create a device record for that sessionToken, because it's pretty definitely a > device using sync We should attempt to perform FxA device registration before calling /certificate/sign, if possible. That call happens as part of the "Cohabiting" state action, right before we move into "Married" state ("good to sync!"). Device registration currently happens once we're in the "Married" state. See  and .  https://bugzilla.mozilla.org/show_bug.cgi?id=1332858#c7  https://dxr.mozilla.org/mozilla-central/source/mobile/android/services/src/main/java/org/mozilla/gecko/fxa/login/Cohabiting.java?q=path%3ACohabiting.java&redirect_type=single#27  https://dxr.mozilla.org/mozilla-central/source/mobile/android/services/src/main/java/org/mozilla/gecko/fxa/sync/FxAccountSyncAdapter.java#541
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
You need to log in before you can comment on or make changes to this bug.