Child Item

DropBox API auth error - {".tag" = "expired_access_token"}

Garnik G.

Language Swift

iOS Version 14.4

We have app where we use dropbox api to allow our users to upload a document.

This app used to working perfectly two years ago.

Very recently we made some small changes and trying to publish now.

DropBox API returns the following annoying error.

API Auth error - {".tag" = "expired_access_token";}

Please explain why in this version I am having this issue.

Find more posts tagged with

API

Abuse

Comments

ernstMreicher58

If your account-level is higher than basic then try a support ticket.

They should be able to help you faster.

Garnik G.

Why dropbox become such an **bleep**?

Is there anybody from dropbox who can read this and try to help.

I can't find any way to contact them.

Maybe we should cancel the subscription.

Greg-DB

The new short-lived access tokens used by the Dropbox API do expire after four hours, at which point you'd get this 'expired_access_token' error. In that case, you would either need to have the user re-authorize the app to get a new short-lived access token, or if the app requested "offline" access, use the refresh token to get a new short-lived access token programmatically. You can find more information on this in the OAuth Guide and this blog post.

You mentioned you're using Swift, but you didn't mention if you're using the official SwiftyDropbox SDK. If you are using that SDK, it should do all of this work for you, including setting up and using "offline" access, as long as you're using a recent version of it and set it up as documented (i.e., using authorizeFromControllerV2).

If something's not working as expected, I'll be happy to help, but I'll need some more information. In that case, please reply with:

the name and version number of the platform and SDK/library you are using, if any
the steps to reproduce the issue, including relevant code snippet(s), but don't include any access/refresh token(s)

Garnik G.

I use SwiftyDropBox which was install by pod

The version number is 7.0.1

Please note this code was working fine before.

I do not use any access_token

What I use is this

DropboxClientsManager.setupWithAppKey("<my key>")

And this is the function I call when user click to dropbox button

func sendUsingDropBox() {

let dbClient = DropboxClientsManager.authorizedClient

if (dbClient != nil) {

isDropBoxModalOpened = false

startWI()

dbClient?.files.listFolder(path: "", recursive: true, includeMediaInfo: true).response(queue: DispatchQueue(label: "DbLfSerialQueue")) { response, error in

if let result = response {

self.dbFolders.removeAll()

result.entries.forEach({(metdaData) in

if !metdaData.description.contains("size=") && !metdaData.description.contains("size =") {

self.dbFolders.append(metdaData.pathDisplay!)

}

})

DispatchQueue.main.async {

self.stopWI()

self.showChooser()

}

} else if let error = error {

print(error.description)

DispatchQueue.main.async {

self.stopWI()

let alert = UIAlertController(title: "DropBox", message: error.description, preferredStyle: UIAlertControllerStyle.alert)

alert.addAction(UIAlertAction(title: THAlerts.Ok, style: UIAlertActionStyle.default, handler: nil))

self.present(alert, animated: false, completion: nil)

}

} else {

isDropBoxModalOpened = true

DropboxClientsManager.authorizeFromController(UIApplication.shared,

controller: self,

openURL: { (url: URL) -> Void in

UIApplication.shared.open(url, options: [:], completionHandler: nil)

})

}

Greg-DB

Thanks for the additional information. From this I see you're using the 'authorizeFromController' method. You'll need to switch to using the 'authorizeFromControllerV2' method instead as shown here to support the new flow. Once you do so, the SDK will automatically handle short-lived access tokens and refresh tokens for you so you shouldn't receive 'expired_access_token' for new authorizations.

Garnik G.

Should I authorize the client everytime they hit dropbox button ?

So before I had this code

let dbClient = DropboxClientsManager.authorizedClient

if (dbClient != nil) {

// read files

} else {

//authorize

}

In some reason dbClient is always NOT nil even if I open the app after fresh uninstall.

So is there any specific attributes that I can use to check if user is already authorized or no ?

Greg-DB

You do not need to send the user through the authorization flow every time they want to use the Dropbox integration. You can have them authorize it once, using authorizeFromControllerV2, and the SDK will automatically store the resulting access token and refresh token for you. You can use authorizedClient to check if you already have credentials saved for that user, and use it if so. The SDK will automatically perform the refresh process for you whenever needed.

Note though that the user or app can revoke the authorization at any time though, at which point you would need to have the user re-authorize the app if they wish to continue using the integration.

Garnik G.

You did not answer to my question.

The problem is that DropboxClientsManager.authorizedClient is not nil all the time and I do not know how to check if user is authorized or not.

Please be specific.

Greg-DB

That is how you check. You can check if authorizedClient is nil or not. If it is not nil, that means you have a saved client to use for that user. (And if the app was disconnected from the account server-side, attempting to use it will accordingly fail with an error.)

Garnik G.

Please let me know if I miss anything from the following

1. I remove the app completely from simulator or device

2. I disconnec the dropbox app from my dropbox account

3. I clean and rebuild the code.

4. I run the app and click to dropbox connect button the following function runs

func sendUsingDropBox() {

let dbClient = DropboxClientsManager.authorizedClient

if (dbClient != nil) {

isDropBoxModalOpened = false

startWI()

dbClient?.files.listFolder(path: "", recursive: true, includeMediaInfo: true).response(queue: DispatchQueue(label: "DbLfSerialQueue")) { response, error in

if let result = response {

self.dbFolders.removeAll()

result.entries.forEach({(metdaData) in

if !metdaData.description.contains("size=") && !metdaData.description.contains("size =") {

self.dbFolders.append(metdaData.pathDisplay!)

}

})

DispatchQueue.main.async {

self.stopWI()

self.showChooser()

}

} else if let error = error {

print(error.description)

DispatchQueue.main.async {

self.stopWI()

let alert = UIAlertController(title: "DropBox", message: error.description, preferredStyle: UIAlertControllerStyle.alert)

alert.addAction(UIAlertAction(title: THAlerts.Ok, style: UIAlertActionStyle.default, handler: nil))

self.present(alert, animated: false, completion: nil)

}

} else {

isDropBoxModalOpened = true

let scopeRequest = ScopeRequest(scopeType: .user, scopes: ["account_info.read", "files.content.write", "files.content.read", "files.metadata.write", "files.metadata.read"], includeGrantedScopes: false)

DropboxClientsManager.authorizeFromControllerV2(UIApplication.shared, controller: self, loadingStatusDelegate: nil, openURL: { (url: URL) -> Void in

UIApplication.shared.open(url, options: [:], completionHandler: nil)}, scopeRequest: scopeRequest)

}

And what happens is that dbClient is not NULL and because of that it returns an error.

In my understanding dbClient must be NULL because everything was cleaned and removed.

What I miss here?

Greg-DB

Even if you've uninstalled the app, the client may still be saved locally since that's persisted in the iOS keychain. And if you've disconnected the app via the Dropbox web site, the SDK won't yet know that the connection has been revoked on the server until you attempt an actual API call, like listFolder, at which point you'll get an authorization error.

You can just call authorizeFromControllerV2 again to prompt the user to re-authorize the app. Or, if you do want to explicitly remove the local client, you can call unlinkClients at any time.

Garnik G.

That is not a solution.

I can't write temporary code. I need to have normal way to verify if dbClient is valid object or not.

What if user want to connect another account.

There must be better approach.

Greg-DB

I'm not sure understand what you mean what you mean by "temporary code". The authorization flow with authorizeFromControllerV2 works effectively the same as it did with authorizeFromController, since the SDK handles the refresh flow for you. Just like with authorizeFromController, you can just process the authorization flow with authorizeFromControllerV2 and let the SDK handle the access token details for you. You would check and use authorizedClient the same way in both cases. (While authorizeFromControllerV2 uses short-lived tokens in its implementation, it works the same way for the app's code as before, since it maintains long-term access using refresh tokens automatically just like the SDK previously maintained long-term access using long-lived access tokens from authorizeFromController.)

If you want to have the user switch to a different account, you can call authorizeFromControllerV2 again and it will replace the authorizedClient.

I recommend following the instructions in the current documentation. If something isn't working as expected/documented, please show both the steps/code you're using, as well as the full unexpected error/output.

Garnik G.

OK. I will try to see if it works also for other users. Thanks for help