Greg-DB Dropbox Community Moderator

@"BattleShip" If you'd like to write some code to programmatically export events from your Business team, you could use the /2/team_log/get_events[/continue] endpoints. Those are links to the documentation for the HTTPS endpoints themselves, but we recommend using one of the official SDKs if possible. Those have…

Based on the context and version number you supplied, it sounds like the you're using the official Dropbox API v2 Java SDK. Can you also share the relevant code snippet(s) (but don't include any access/refresh token(s)), as well as the steps you're following when this issue occurs? Thanks in advance!

Thanks for the feedback! I'm sending this along to the team.

I'm glad to hear you were able to get it working already. For reference though, it's technically safer to parse the URL and set the parameter, instead of just adding it as a string. For instance, you could do something like: var modifiedAuthUrl = new URL(authUrl);modifiedAuthUrl.searchParams.set('force_reapprove',…

The official Dropbox JavaScript SDK doesn't have the 'force_reapprove' option built in, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. You should be able to add that to the URL returned by getAuthenticationUrl though. Can you share what you have so far, and what…

1A) The creation of new long-lived access tokens is now considered deprecated, but we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s). You do not need…

I'm not sure I understand your message. Did you resolve the issue or do you still need help from Dropbox?

If you need a non-temporary link, you can instead use /2/sharing/create_shared_link_with_settings to get a shared link. You can also modify those shared links for different behaviors as documented here.

That 'http.Start' call starts the local web server which is used to catch the redirect from the app authorization flow. The error message seems to be indicating that the server can't be started, perhaps because that port is already in use. Is there anything on that computer using that port, or do you maybe accidentally…

That should be fine. The upload session endpoints support uploading files up to 350 GB in size.

[Cross-linking for reference: https://github.com/dropbox/dropbox-sdk-js/issues/769 ] I've followed up on your GitHub post.

No, unfortunately, the Dropbox API doesn't offer the ability to retrieve the time a file was opened and not modified like that, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The standard way to download a file via the Dropbox API is the /2/files/download endpoint. That returns the file data directly in the response body. If you do need a URL that you can use to download the file, you can call /2/files/get_temporary_link. That will return a link that you can use to access the file data later…

Is that the full error/output? If there's any other error/output, please share that for reference. You may also be able to enable more verbose output by using curl's "-v" option. From what you shared here though, I see you're getting "Address unavailable", which may indicate a DNS issue. The 'api.dropboxapi.com' domain is…

Have you checked the suggestions in my last message?

Any endpoint using "User Authentication" (or "Team Authentication") does require an access token. That includes both the download and the "upload session" endpoints, for uploading large files. The access token can be either a legacy long-lived access token, or a short-lived access token. So, if you're using a short-lived…

The team is reporting that this issue is now fixed and should be working properly. Apologies for any inconvenience this may have caused, and thanks again for bringing this to our attention.

If everything in the connected account accessible to the app is public anyway, that would allay concerns about data leakage at least. There may still be issues with exposing the ability to perform other API calls, such as uploading files, but that could be minimized by restricting the refresh token (and consequently the…

The Dropbox API does offer the ability to programmatically generate file requests, via the /2/file_requests/create endpoint. This isn't restricted to any particular platform(s). You can make Dropbox API calls anywhere you can perform HTTPS requests. I can't offer guidance for Woocommerce/Wordpress/Trello in particular…

I recommend trying out the Embedder to see if it works for your use case. That would be the safest way to do this. That works by supplying it a shared link to the folder you want to display. Otherwise, you would need to use the API, which would require a refresh token for this scenario. Like the now-deprecated long-lived…

This looks like it may indicate an issue with the installation of the Dropbox library in your project. How did you install the Dropbox library, and what output did you get when you did? If something went wrong, it may help to try to uninstall and reinstall it.

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…

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…

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.)

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…

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…

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…

No, unfortunately the Dropbox SDKs don't officially support React Native.

It sounds like you're describing the app authorization flow built in to the official Dropbox mobile SDKs. You can find those here: * for Swift on iOS: https://github.com/dropbox/SwiftyDropbox * for Objective-C on iOS: https://github.com/dropbox/dropbox-sdk-obj-c * for Java: https://github.com/dropbox/dropbox-sdk-java (see…

Another update: SwiftyDropbox now supports Alamofire 5 as of v8.0.0.