1794205 - Adding a new device capabilities: considerations

Status: NEW

(Firefox for Android :: Accounts and Sync, task)

Description

[Jonathan Almeida [:jonalmeida]]

From github: https://github.com/mozilla-mobile/android-components/issues/8164.

In https://github.com/mozilla-mobile/android-components/pull/7856 we're changing how ensureCapabilities is treated: as a method which isn't expected to do any networking (and thus, randomly fail) during regular account rehydration flow (e.g. startup). All of the work is done within initializeDevice. See https://github.com/mozilla/application-services/issues/3474.

However, this assumption breaks if we've added a new device capability. Then we probably do need to do some fallible work as part of ensureCapabilities, which introduces a failure point to our startup path. This issue is to think about how to handle that best, when the time comes.

cc @rfk @eoger

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.