-
Notifications
You must be signed in to change notification settings - Fork 207
Open
Description
Our users have been reporting issues where they keep getting signed out of Dropbox after quitting the app and relaunching.
This is how we're doing our setup and auth:
- on app launch,
DropboxClientsManager.setupWithAppKey(.apiKey)
is called - sign in using
DropboxClientsManager.authorizeFromControllerV2
- call
DropboxClientsManager.handleRedirectURL
- now DropboxClientsManager.authorizedClient is not nil.
- on next app launch, we call
DropboxClientsManager.setupWithAppKey(.apiKey)
again, butDropboxClientsManager.authorizedClient
is still nil for some users.
after further digging into handleRedirectURL
call, I found this line where result of storeAccessToken
is ignored. In the case of storeAccessToken
returns false, the access token is not persisted for next app launch.
This could mean that for those problematic users, after calling DropboxClientsManager.setupWithAppKey(.apiKey)
, it may fail to setup authorizedClient in this line.
I can't verify this though or inform users why it fails since there's no logging visible from my app. Could someone help?
Metadata
Metadata
Assignees
Labels
No labels