You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An API is exposed to get the external urls used to managed the account: fun accountUrl(action: AccountManagementAction?).
The applications are using this API to display the 2 settings entries "Manage account" and "Manage devices", if the respective returned URL are not null, and on click action open the webpage, see below:
But this API is performing network request and so can be slow to return, or can even fail when there is no network.
This will lead the application to:
not show the entries in the root setting screen (no network)
delay the display of the entries (slow network)
To solve this, the SDK should prefetch the URL for the actions AccountManagementAction.Profile and AccountManagementAction.SessionsList, in order to speed up the return of the method fun accountUrl(action: AccountManagementAction?).
Not sure when the cache should expire, it's maybe safer to always fetch the URL at each client creation.
Note: mechanism used to pre-fetch data about the user, such as avatarUrl and displayName could be reused to solve this issue.
The text was updated successfully, but these errors were encountered:
An API is exposed to get the external urls used to managed the account:
fun accountUrl(action: AccountManagementAction?)
.The applications are using this API to display the 2 settings entries "Manage account" and "Manage devices", if the respective returned URL are not null, and on click action open the webpage, see below:
But this API is performing network request and so can be slow to return, or can even fail when there is no network.
This will lead the application to:
To solve this, the SDK should prefetch the URL for the actions
AccountManagementAction.Profile
andAccountManagementAction.SessionsList
, in order to speed up the return of the methodfun accountUrl(action: AccountManagementAction?)
.Not sure when the cache should expire, it's maybe safer to always fetch the URL at each client creation.
Note: mechanism used to pre-fetch data about the user, such as
avatarUrl
anddisplayName
could be reused to solve this issue.The text was updated successfully, but these errors were encountered: