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...
Greg-DBDropbox Staff
Dropbox StaffRobert 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.
- Greg-DB
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 note. The system should automatically use the latest available version. The Java and Python SDKs were only called out in particular since those were more recent and contained code that would affect the version used. If you need help confirming anything for your app(s) in particular, please open an API ticket.
Ah, I see. I read the date 11/3/2020 as being in March (being based in the UK), so assumed you were suggesting that he update to a later SDK. I see now that he meant (or at least you thought he meant) that it was an SDK from November, which you were confirming should be fine. All good.
Even without a specific test for use of the deprecated protocols, there is one thing Dropbox could do to help us know if we have a problem with our latest version. In the e-mail that goes out to developers telling them that they detected "some activity" with the deprecated protocols, why not include something more quantitative? Tell us, for instance, the percentage of deprecated uses. If our current versions are indeed faulty, then 100% of the accesses will involve the deprecated protocols. But if only 7% of the accesses are problematic, then we can rest easy knowing that the 7% must represent users who have not updated their apps. Dropbox has the data, right?
- Greg-DB
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.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
