Mendix Native App Review for iOS with Mx10 upgrade

0
Hello,   We are trying to update our Native Mobile Mendix App since we've upgraded our development environments from 9.24.40 to 10.24.11. We have built and tested doing this upgrade on Test and Acceptance environments, where our backend/runtime is on Mx10 already in Sprintr.   For these two environments we have successfully pushed our changes to iOS App Store Connect, where we can test in Testflight and everything seems to work. This is possible because there is no actual production dependency, and Apple doesn't need to test our app here.   Our issue right now is that we need to now do the same for our Production environment. We have built the Native App based on our Acceptance branch, and it is successfully built and pushed to our Production environment on App Store Connect. We published the build for Review by Apple, as that is necessary before we are allowed to deploy it to the App Store. However, because our Production runtime is still on Mendix 9, it seems the app crashes when Apple tries to open and test the app. (I know it's an assumption to say it's because of the mismatch between Mx9 and Mx10 runtimes, but it seems the most logical explanation).    We cannot, and also don't want to, release our Production runtime to Mx10 while the users are still using builds made in Mx9 because we don't want to risk crashing their apps. We're kind of in a loop here, as the one can't reliably be deployed without the other.   I wasn't able to find any proper documentation on this, and Apple just keeps replying that they need to not have crashes when testing. Does anyone have any experience with this? Tips? Best practices? Advice?   Thanks in advance
asked
2 answers
0

I would suggest to keep two builds. Old one to keep v9 working without any impact and new version of Mx10 build that will be used for apple review.. 

 

  • Freeze Production deployments (so old Mx9 apps don’t get risky OTA).

  • Build Mx10 native app from Acceptance (or review branch).

  • Point that build to a Mx10 review backend.

  • Submit ->  Apple approves (no crash).

  • Release Mx10 app to store (phased rollout).

  • Upgrade Production runtime to Mx10.

  • Unfreeze OTA / resume normal ops.

answered
0

Hi Gina,

Our strategy to migrate from Mx9 to Mx10 was:

- Have a recent Mx9 build based on your latest Mx9 model (possibly without any OTA updates)

- Upgrade Mx9 model to Mx10 and only update neccesary Marketplace modules so you don't have any run/build errors anymore. Make no functionality changes what so ever. 

- Create new Mx10 build based on Mx10 branch

- Deploy Mx10 branch to environment

-- Mx9 build will not receive OTA due to incompatible client (no errors, just silent log message on backend)

- Let Apple/Google review your Mx10 build

- Release build and give your users some time to update their app

-- Possibly use a mechanism to check local build with latest build and present user with update page to enforce updating

- OTA update all your other new functionality just like you are used to

answered