Support statement for new requirements on MobileFirst Platform Foundation v7.1
Srihari Kulkarni October 15, 2020
MobileFirst_Platform MobileFirst_Foundation iOS
Listen to the post excerpt
MobileFirst Platform Foundation version v7.1 is approaching its end of support, which is on March 31, 2020. Any upcoming requirements or deprecations from the Apple or Google ecosystem are considered new features, and therefore will not be supported even under an extended support contract. This applies to the following list of upcoming requirements.
-
Use of UIWebView - New apps containing UIWebView will not be accepted to the Apple App Store, starting April 2020 and app updates using UIWebView from December 2020. [Update: Apple has extended the deadline for removal of UIWebView beyond December 2020.]
-
Use of legacy binary protocol for Push Notifications - Apple has notified developers about switching to HTTP/2 based APNs provider for sending push notifications. Starting from November 2020, all notifications should be sent over the HTTP/2 protocol. [Update: Apple has extended this deadline to March 31, 2021]
-
Support for new mobile OS releases - Support for new OS releases for all supported platforms such as Android, iOS, and Windows when available will not be made available on MobileFirst Platform Foundation v7.1.
Note: This is not an exhaustive list and any new requirements or deprecations from Apple or Google in the future, will also be considered as new features.
Mobile Foundation v8.0 accounts for the above changes and will provide support for new and upcoming mobile OS versions. Therefore, if your apps are running on MobileFirst Platform Foundation v7.1, especially the ones that are published to public app stores, we strongly recommend you to migrate to Mobile Foundation v8.0 at the earliest to avail continued support for new mobile OS versions and developer ecosystem changes.
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.