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
Hi, my app is using non-scoped Dropbox client (old auth flow).
After my app starts and call to DropboxClientsManager.setupWithAppKey(#APIKEY) is done, I use DropboxClientsManager.authorizedClient != nil to check if the user is signed in.
For some users, authorizedClient often becomes nil and they'll need to sign in again.
Is this bug because I'm using old auth flow? or am I just doing it wrong?
If I change my app to use scoped from dashboard, will it cause my users on old clients to lose access?
Thank you for your help!
The text was updated successfully, but these errors were encountered:
If you are still using the old authorizeFromController method in particular though, you should migrate to the new authorizeFromControllerV2 method. You can use the authorizeFromControllerV2 method whether or not you have migrated your app to use scopes. If you have not migrated your app to use scopes, you would set the scopeRequest parameter to nil.
If you're still having trouble, I'll be happy to help with any issues you're having with the Dropbox API/SDK, but I'll need some more information. Please reply with:
the version number of the SwiftyDropbox SDK you are using
the steps to reproduce the issue, including relevant code snippet(s), but don't include any app secret, access or refresh token(s)
Hi, my app is using non-scoped Dropbox client (old auth flow).
After my app starts and call to DropboxClientsManager.setupWithAppKey(#APIKEY) is done, I use
DropboxClientsManager.authorizedClient != nil
to check if the user is signed in.For some users,
authorizedClient
often becomesnil
and they'll need to sign in again.Thank you for your help!
The text was updated successfully, but these errors were encountered: