IBM MobileFirst Platform Foundation Support for iOS 13

If you are an on-premise 7.1 or 8.0 customer or Mobile Foundation Service customer, then read further to learn about Mobile Foundation support for iOS 13.

Apple announced iOS 13 during their annual WWDC2019 conference. You can read more about all the new features in iOS 13 here.

We have been testing the iOS 13 beta with the latest being beta 3. We have verified various features of MobileFirst Platform Foundation on the iOS 13 beta 3 for MobileFirst Platform Foundation v7.1 and v8.0. For reference, make sure to read through our support plan for newer iOS version.

We encourage you to start testing your application(s) with iOS 13.

MobileFirst Platform Foundation Support for iOS 13 (beta 3)

Existing application

Existing application(s) that were created using MobileFirst Platform v7.1 and v8.0 will work on iOS 13 as they did on previous versions of iOS.

Compatibility tests with iOS 13 beta 3 have been performed using an iPhone 7 that was upgraded from iOS 12.3 to iOS 13 beta 3 for MobileFirst Foundation v7.1 and v8.0.

For the tests, XCode 11 beta 3 was used to compile native, hybrid and Cordova apps.

Submitting application to App Store

Apps built with older Xcode(10.1 and above) can still be submitted to App Store. The minimum iOS SDK level 12.1 should be used in any newer or existing apps. Refer here for details.

Swift Apps on iOS13

Xcode 11 build can build targets written in only Swift 4.0 or above. Swift 5.0 with ABI is available since Xcode 10.2, migration tools are available with Xcode 13 as well to migrate to Swift 5.0.

As per Apple you can submit apps in Swift 4.0 to the App Store and migrate individual modules to Swift 5 when you are ready. We strongly encourage you to migrate your code to Swift 5.0.

Features that were tested for Mobilefirst Foundation (MFP) v8.0:

  • OAuth Flow
  • Invoking backend procedures through adapters
  • Challenge Handling
  • JSONStore
  • Direct Update
  • Secure Direct Update
  • Application Management
  • Application Authenticity
  • Remote Disable
  • Device SSO
  • Push notifications
  • Certificate Pinning

Features that were tested for Mobilefirst Foundation (MFP) v7.1:

  • JSONStore
  • Direct Update
  • Application Management
  • Application Authenticity
  • Remote Disable
  • Device SSO
  • Push notifications
  • Certificate Pinning

Known Issues

Too Many HTTP Redirect on v7.1

While Testing OAuth Flow on v7.1 we found the following issues in App.

too many HTTP redirect

The feature impacted because of the issues are

  • OAuth Flow
  • Invoking backend procedures through adapters
  • Challenge Handling

Update: We don’t see Too Many HTTP Redirect issue anymore with iOS 13 beta 8. Therefore, we are not publishing any fixes for the issue.

CNCopyCurrentNetworkInfo Returns Nil

MobileFirst SDK for v7.1 makes use of CNCopyCurrentNetworkInfo inside Device->wifi->getConnectedAccessPoint API. As per Apple iOS 13 guideline one of the following conditions should be met in order to get a correct response from CNCopyCurrentNetworkInfo, else it returns nil.

  • The app uses Core Location, and has the user’s authorization to use location information.
  • The app uses the NEHotspotConfiguration API to configure the current Wi-Fi network.
  • The app has active VPN configurations installed.

Learn more by reading the updated documentation or viewing the the Advances in Networking session video from WWDC19. Also refer here, for more details.

Apple further recommends If your app is using this API, we encourage you to adopt alternative approaches that don’t require Wi-Fi or network information. Valid SSID and BSSID information from CNCopyCurrentNetworkInfo will still be provided to VPN apps, apps that have used NEHotspotConfiguration to configure the current Wi-Fi network, and apps that have obtained permission to access user location through Location Services.

Push Notification Registration Issue

While fresh installation of apps using MobileFirst Push notification on iOS 13, regresitration is failing due to error in parsing the token from APNS server. The issue is similar to one reported on Apple developer Forum.

Note Customer should upgrade to cocopod version IBMMobileFirstPlatformFoundationPush@8.0.2019082914 for v8 native app and npm version cordova-plugin-mfp-push@8.0.2019090606 for v8 cordova apps. For MFP v7.1 install iFix version 7.1.0.0-MFPF-IF201909091200 or higher.

WatchOS 6

We have verified basic OAuth Flow and Application Authenticity on watchOS 6.

iPadOS 13

iPadOS 13 doesnt have a separate SDK with Xcode 11 beta. So we have not done any separate testing for iPad OS. iPAD avilable with Xcode11 still using iOS 13 only.

iPadOS 13 deployment info

xcode11SDKs

Update: We had used iPadOS 13 beta restore images on iPad and verified all Major features of MFP. We found an issue with Direct Update feature only for ionic apps. We are investigating further.

We have also verified MFP based cordova, ionic and react-native apps.

All the above features were validated to work on iOS 13 beta 3.

iOS 13 compatibility tests are planned for the following:

  • Application Center

Stay tuned for further updates.

Disclaimer: Some of the action items that are addressed in the list above are not under IBM’s control. Therefore, we expect developers and IT managers to ensure that their infrastructure is up-to-date according to Apple’s requirements.

Last modified on September 10, 2019