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


iOS 9 Bitcode Support and Salesforce Mobile SDK

In iOS 9, Apple introduced bitcode support. Bitcode images offer benefits for apps uploaded to iTunes Connect, as described here.

Salesforce Mobile SDK for iOS will add iOS bitcode support in its upcoming 4.0 release. However, if you’re a GitHub user and you just can’t wait–chafing at the bit, as it were–you can add this feature to your existing Mobile SDK 3.3 apps right away. Just “cherry-pick” the following pull request and apply it to your copy of Mobile SDK:

Please note that:

  • Bitcode-enabled binaries are backwards compatible with iOS 7 and 8. However, the benefits of using bitcode apply only to iOS 9.
  • You can use bitcode-enabled static libraries in XCode 6 and 7. XCode 6 simply ignores the bitcode flag.

Tips for Upgrading Mobile SDK Apps for iOS 9

iOS 9 is here, and we’ve got a couple of tips for how to update your Mobile SDK apps.

If at all possible, you should update your app to Mobile SDK 3.3.1 (or later), and then apply the fix in Tip #1. If you’re unable to update at this time, you should implement both Tip #1 and Tip #2.

Tip #1

In iOS 9, Apple introduces an Application Transport Security feature for secure network connections. See https://developer.apple.com/library/ios/technotes/App-Transport-Security-Technote/ for a list of their requirements.

Salesforce servers use TLS 1.2 but do not yet support forward secrecy. Until they do, Mobile SDK apps need to disable the forward secrecy requirement. If you created your app with Mobile SDK 3.3.1 or later, you don’t need to change anything. If your app is based on Mobile SDK templates from a version earlier than 3.3.1, add the following configuration to your application plist:


To see these how we made these changes for Mobile SDK 3.3.1, check out https://github.com/forcedotcom/SalesforceMobileSDK-iOS/pull/1170.

Tip #2

iOS 9 introduces subtle behavior changes in the unarchiveObjectWithFile: method of NSKeyedUnarchiver. Due to these changes, users automatically get logged out after restarting any iOS Mobile SDK app built with Mobile SDK 3.3 or earlier. We’ve fixed this issue in the Mobile SDK 3.3.1 release. We urge all iOS developers to update to Mobile SDK 3.3.1 (or later). Otherwise, your application won’t behave properly on iOS 9 devices.

If for some reason you can’t upgrade to 3.3.1 (or later) at this time, you’ll need to edit the SDK source code and rebuild the SDK. Here are the details for manually addressing this issue:

The unarchiveObjectWithFile: message of the NSKeyedUnarchiver class now returns nil upon failure, instead of throwing an exception. You’ll need to update SFUserAccountManager.m manually as shown here:

After making the change, rebuild the Mobile SDK libraries and then use them to rebuild your app.

Salesforce Mobile SDK 2.2.0 is Now Available

Salesforce Mobile SDK 2.2.0 is live!

Grab the latest here:

On GitHub – https://github.com/forcedotcom/SalesforceMobileSDK-Android/tree/v2.2.0
On npm – https://npmjs.org/package/forcedroid

On GitHub – https://github.com/forcedotcom/SalesforceMobileSDK-iOS/tree/v2.2.0
On npm – https://npmjs.org/package/forceios

Release Notes:
Android – https://github.com/forcedotcom/SalesforceMobileSDK-Android#whats-new-in-22
iOS – https://github.com/forcedotcom/SalesforceMobileSDK-iOS#whats-new-in-22

Salesforce Mobile SDK Development Guide (browser download):