Role-based nanoflow for nativePhone - Mendix 10.24

0
In mobile native app, I have set role-based nanoflows to start application with: First it goes the "Anonymous" path, where user logs in, followed by app reload. Afterwards it goes the "User" path. Since upgrade from Studio 9 to 10, it doesn't work anymore. What does Mendix check on client 10 to determine the "User" path? In terms of entities, session, system variables...?
asked
1 answers
0

This issue is caused by database/metadata incompatibility after a major version upgrade, not by a browser or theme problem.

The earlier “Unsupported pre-analysis migration version” error in Mendix 9 already indicated that the database was not fully compatible. In Mendix 10, that specific error is no longer thrown, but the client fails silently when it encounters incompatible metadata during UI initialization.

That’s why:

  • Images (static assets) still load
  • Text and video content (data-driven UI) do not render
  • No clear runtime error is shown

Why this happens

Between Mendix 9 and 10, the client lifecycle, metadata handling, and async data loading changed. If the existing database contains incompatible system or model metadata, the React client stops rendering parts of the UI without throwing visible errors.

How to confirm

Run the app with a fresh, empty database:

  • If the UI loads correctly → the old database is incompatible
  • This confirms it’s a data/metadata issue, not static content

Recommended fix

  • Do not reuse the Mendix 9 database after a major upgrade
  • Start with a new database
  • Recreate or re-import data (CSV/ETL)
  • Enable verbose logging only for deeper inspection


answered