You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Greg-DB
Dropbox Staff
Dropbox StaffReminder: 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 a...
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.
Greg-DBDropbox Staff
Dropbox StaffRobert 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.
Can you at least confirm that the following is sufficient for avoiding the deprecated protocols:
In the Android version of our app, the build.gradle file under the app folder contains:
dependencies {
. . . .
implementation 'com.dropbox.core:dropbox-core-sdk:3.1.5'. . . .
}and in the iOS version of our app, all the files in all the subdirectories of:
Pods/ObjectiveDropboxOfficial
have a file date of 11/3/2020.
If it is not sufficient, tell me what else I could check.
- Greg-DB
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.
Hi Greg. It would be good to clarify the exact versions involved here for various SDKs. Just to recap what the original email sent out in Aug 2021 said:
1) SDKs over two years old may need updating (so I presume from Aug 2019 and earlier).
2) The Java and Python SDKs have specific versions that need updating to
Based on that I had no concerns since I was not using an SDK that old, and was not using either of the SDKs mentioned. So I am a little surprised to see you mention that the Obj-C SDK may need updating to late 2020, since this is obviously later than 2019, and the SDK was not mentioned in the original email. Could you please clarify what is the exact minimum version number of the SDK required to update to for the following versions of the SDK:
1) Objective-C
2) .NET
Many thanks.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
