Disabling TLS 1.0: Preparing Mobile SDK Apps for the Big Change

A big change is coming! Originally it was announced as occurring in early 2016, but it’s now been postponed until 2017 for production instances (June 2016 for sandbox instances). Please read this post for the full details: https://developer.salesforce.com/blogs/engineering/2016/03/disabling-tls-1-0-preparing-mobile-sdk-apps-big-change.html


2 thoughts on “Disabling TLS 1.0: Preparing Mobile SDK Apps for the Big Change

  1. Jason Clark

    I have a couple of mobile apps that for the time being will use option B for android (apply the patch – client’s choice). I’ve built the app and it runs; any way to test & confirm(e.g., prove to the client) it is TLS1.1-ready before submitting to the Play store?

    1. rwhitleysfdc Post author

      Hi Jason,

      Near the bottom of this knowledge article–https://help.salesforce.com/HTViewSolution?id=000221207&language=en_US–there is a procedure for testing REST API clients by changing the login server to tls1test.salesforce.com in a test environment. Please read the article for details on interpreting the result of your test.

      Best regards,


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s