Beginning on or after April 13, the Dropbox API will require that calls use TLS 1.2 or greater. Traffic using TLS 1.0 or 1.1 will be rejected. The latest Dropbox SDKs will select TLS 1.2 when available in the environment, but versions over two years old may require an update. In particular, users of the Dropbox Java SDK should update to v3.1.1 (released June, 2019) or later & Dropbox Python SDK should update to v8.4.1 (released November, 2017) or later. TLS 1.2 has been the default on major mobile & desktop operating systems since 2014. Developers whose application may be run in older or unusual environments should investigate to ensure compatibility. Please ensure your apps use TLS 1.2 when connecting to the Dropbox API.

Hi Dropbox, We are currently using the following version in the Android apps. implementation 'com.dropbox.core:dropbox-core-sdk:2.1.1' We will update to the required version. But development, testing and user update will take much more than 1 month left. We ask Dropbox to give us more time to comply. Thanks for the consideration.

I received an e-mail from Dropbox warning that "your app(s) TuneLab Tuning Files have recently made calls to the Dropbox API using a deprecated TLS protocol version." I thought we had updated both our iOS and Android versions over a year ago. I suppose it is possible that some users of our apps have not updated in all that time, but I would like to know if there is any test I could run to see whether or not the latest versions of my apps are using the deprecated protocol. My inspection of the Android code shows the external library of com.dropbox.core:dropbox-core-sdk:3.1.5, which should be OK. And the iOS code uses cocopods and references ObjectiveDropboxOfficial and a README.MD that says "The Official Dropbox Objective-C SDK for integrating with Dropbox [API v2] " which should be OK too. The source files are dated 11/3/2020. So that should be OK too. But I don't trust this as proof that my apps are not using the deprecated protocol. So how can I run a test to know for sure? Is there a way I can simulate April 13th now? Or monitor traffic? The e-mail I got from Dropbox has got me worried.

I would second that request of a simple test for peace of mind. I also got that email, but my apps have should have been using compliant versions of the SDK for many years...

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, perhaps they were caught by a spam filter. Please make sure that the email address on the account that owns your API app(s) is correct and can receive email. Additionally, make sure you haven't unsubscribed from "API announcements".

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 if or when that might be implemented though. If you'd like additional help verifying this, feel free to open an API ticket from the account that owns the app(s) in question and we may be able to offer some help.

Forum Discussion

Greg-DB

Dropbox Community Moderator

4 years ago

Reminder: The Dropbox API will no longer accept TLS 1.0 or 1.1

Beginning on or after April 13, the Dropbox API will require that calls use TLS 1.2 or greater. Traffic using TLS 1.0 or 1.1 will be rejected.

The latest Dropbox SDKs will select TLS 1.2 when available in the environment, but versions over two years old may require an update. In particular, users of the Dropbox Java SDK should update to v3.1.1 (released June, 2019) or later & Dropbox Python SDK should update to v8.4.1 (released November, 2017) or later.

TLS 1.2 has been the default on major mobile & desktop operating systems since 2014. Developers whose application may be run in older or unusual environments should investigate to ensure compatibility.

Please ensure your apps use TLS 1.2 when connecting to the Dropbox API.

API

22 Replies

dodnewtech50
New member | Level 2
4 years ago
Hello there,

I am attempting to update my application to be able to work with TLS 1.2. I have updated my dropbox module to version 11.7.0 in pythonista. Now I get the following error: Timeout value connect was Timeout(connect=100, read=100, total=None) but it must be an int or float

I have two questions: 1) Do you have any suggestions on how to address this error?
2) Do I need to update my API token now that I've made these changes?
Greg-DB
Dropbox Community Moderator
4 years ago
dodnewtech50

1) I believe that was a bug in an older version of the 'requests' library. Please update the version of 'requests' you have installed and try again.

2) No, these TLS changes do not require you to change your access token(s).

About Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!

Forum Discussion

Reminder: The Dropbox API will no longer accept TLS 1.0 or 1.1

22 Replies

About Dropbox API Support & Feedback

Related Content

Dropbox transfer thumbnail no longer shows on WhatsApp

Why is the Dropbox Desktop App no longer available?

Dropbox no longer works on my MAC 10.11.6.

Sync icons are no longer visible after Dropbox update on Windows

I can no longer use the Dropbox for Outlook integration.

Recent Discussions

Shared Link - Download in .NET

Dropbox API server root certificate changes for .Net

GetCurrentAccountAsync API Failing for some Team Members while using Impersonation

Find DBID on Local PC

How to replace a non-existent permanent token? Any auto-refresh alternative for automation?