MobileFirst Foundation iFix 126.96.36.199-IF20170220-1900 released
A new iFix has been released for MobileFirst Foundation 8.0, dated February 20th, 2017.
Changes in this iFix
For a cumulative list of all previous fixes, see the iFix download page on IBM Fix Central.
Dynamic App Authenticity
This iFix introduces a new implementation of Application Authenticity. This implementation does not require the offline mfp-app-authenticity tool for generating the .authenticity_data file. Instead, you can enable or disable Application Authenticity from the MobileFirst console. For more information see Configuring Application Authenticity.
Important: Android, iOS, Windows, Xamarin, Web & Cordova applications built with iFix 8.0.0.00-20170216-202020 will require a minimum server version of 8.0.0.00-20170216-202020. If you’re using an older version of the server, please upgrade your server by downloading the latest build from FixCentral or from the Downloads page.
If you are using Mobile Foundation on IBM Bluemix, please Re-create the server with the updated version.
Note: The server behavior during Re-create would vary depending on the plan selected. Refer to the Mobile Foundation documentation for more information.
PI75479 BITCODE NOT SUPPORTED IN MFP V8.0
PI72424 INCORRECT SERVERS DISPLAYED FOR NODE IN SERVER CONFIGURATION TOOL
PI66415 OUR DEFAULT SCOPE IS EMPTY STRING AND WE CHANGE IT TO: “REGISTEREDCLIENT”.
How to upgrade
To upgrade, download & install the Developer Kit for evaluators, Developer Kit for customers / iFix package for on-prem production environment (requires login to IBM Fix Central), or refresh your Mobile Foundation service from your service Dashboard.
To upgrade, run the upgrade commands for your platform.
Individual artifact build numbers included in this iFix
Server runtime 8.0.2017021501
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.