Greg-DB Dropbox Community Moderator

Yes, as you found, Dropbox is phasing out the ability to create new long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access…

@"af11" Thanks for following up. I'm glad to hear you got that working. Your new question seems to be related to using Google to sign in to Dropbox, and the level of access used in that flow. We can only help with the Dropbox API itself here, so I recommend opening a thread in the accounts section of the forum or…

@"Robert S.138" Thanks for the feedback/idea! I can't make any promises myself, but feel free to open an API ticket if you'd like to request specific help/information.

Thanks for the additional information! We'll look into it and I'll follow up here once I have an update on this.

Thanks for following up. This file size limit has not changed recently. Uploading 1 Gb files in 8 Mb chunks is supported. To clarify, are you still seeing this issue on new requests now? And if so, is this occurring on all such requests, or only some of them? Also, if you can share a more specific date/time of when you…

@"Mark R.5" Thanks for the feedback. To clarify, I was not indicating that one would be required to update to an Objective-C SDK from late 2020. Rather, I was responding to Robert's specific question and confirming that such as version should be sufficient. I don't have specific versions of the Objective-C and .NET SDK to…

@"ephraimt" Yes, the current configuration is what we expect to serve going forward. That is, we are returning Content-Length on both HTTP/2 and HTTP/1.1 for these links, like we did originally. If this is currently not working for you, can you share the details of the current error you're seeing? Also, did this start…

There are a number of scenarios that can cause the refresh to fail like this, such as: * missing/incorrect/malformed refresh token * revoked refresh token (e.g., when the user unlinks the app via https://www.dropbox.com/account/connected_apps , etc.) * missing/incorrect/malformed app key * incorrect/malformed app secret *…

@"Robert S.138" Yes, Java SDK v3.1.5 is sufficient. And likewise a version of the Objective-C SDK from late 2020 would also be sufficient.

@"DreamingDev" 1. If you received that email it means your app sent some amount of TLS 1.0 or 1.1 traffic to the Dropbox API recently. If you’ve already updated your app, this traffic is likely coming from users still on an old version of your app. We don't have a way to simulate the change, but I'll pass this along as a…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this on 3/14.…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this on 3/14.…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not ‘Transfer-Encoding: chunked’) in the future and will not be reverting this as…

Update: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as…

@"Robert S.138" @"Mark R.5" If you’ve already updated your app, this traffic may be coming from users still on an old version of your app. You may want to notify your users to update to the latest version of the app. We don't have a way to simulate the change, but I'll pass this along as a feature request. I can't promise…

@"Eric Z.6" Thanks for sharing this feedback. At this time I am unfortunately not able to offer extensions for this change, but I’m sending this feedback along to the team. For reference, we did send earlier advance notices about this change by email last year, but it sounds like those did not make it to you. For instance,…

This should be fixed now. Thanks for the report!

That unexpected error message should be fixed now.

Yes, that's correct. The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. While it is technically possible to always connect to just one account for all users, we do not officially support this, for various technical and security reasons.…

[Cross-linking for reference: https://stackoverflow.com/questions/71426027/how-can-my-non-product-just-for-my-use-swift-app-write-data-to-a-dropbox-file ] You can use the SwiftyDropbox SDK to integrate with Dropbox, even if your integration is not meant to be a released product. You can find instructions for getting…

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. 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 or…

@"justindaw" We're working on some updates that should allow us to avoid that. I should have an official update on this on Friday.

@"lalomores" Just like with long-lived access tokens, the user needs to manually authorize the app once to get the refresh token, which can then be stored and re-used without further manual user interaction. In that example, you can see where the SDK returns the refresh token, which is then set on the client, on this…

@"lalomores" I see you also opened another thread for this. We've followed up with you there.

@"TheWhistler1967" As Здравко mentioned, you can use the API to look up the existing group(s) to get the group ID(s). Then you can use that to build a GroupSelector as needed, like this: dbt = dropbox.DropboxTeam(TOKEN)# just taking the first group as an example:group = dbt.team_groups_list().groups[0]group_selector =…

[Cross-linking for reference: https://stackoverflow.com/questions/71393752/get-a-refresh-token-for-dropbox-api-using-rdrop2-and-drop-auth ] As you found, Dropbox is in the process of switching to only issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more…