9.24.40 SQLLitePlugin Error

0
After upgrading to 9.24.40 and launching the native app, the following error appears in the native logs when attempting to retrieve the user's account using [id = '[%CurrentUser%]'] as the XPATH constraint:SQLitePlugin.executeSql[Batch]() failednet.sqlcipher.database.SQLiteException: no such column: Administration$Account.System$ownerThis has worked with no issues before, so we're wondering if there is something that needs to be updated with the move to 9.24.40?
asked
2 answers
0

First, verify Administration.Account → Store ‘Owner’ is enabled in the entity properties. If the column still isn’t present locally, “touch” it so the native/offline compiler cannot optimize it away: place a temporary (even hidden) widget on a Native page that references Account/System.owner (for example a Text widget inside a hidden container or a hidden Data View). This forces the metadata to include the member in the offline schema.


Then, go to App Navigation -> Native phone profile -> Synchronization configuration and ensure Administration.Account is included for offline sync. If it is already there, remove it and add it back to refresh the offline mapping and regenerate the native bundle/sync model. (Offline sync behavior is driven by the Synchronization configuration for offline-first apps.)


Finally, make sure to rebuild the local database on the device (clear app data / reinstall). Otherwise the device can keep an older SQLite schema and you will continue to see “no such column” even after fixing the model. If you have end users, plan a safe “reset local data” approach (keeping in mind unsynced offline changes).


In short: Store Owner + “touch” System.owner in UI + ensure entity is in Sync Configuration + clear/reinstall to rebuild SQLite.


answered
0

hi,


This error is not caused by your XPath, and it is not a bug in your model — it is a native offline database schema mismatch after upgrading the Mendix version.

What’s happening

When you run a native/mobile app with offline support, Mendix stores most persistent data in a local SQLite database.

After upgrading to a newer Mendix version (e.g. 9.24.x), the model changes slightly (new system columns, metadata, owner flags, etc.), but the old SQLite database remains on the device with the old schema.

So when the native client runs:


SQLitePlugin.executeSql failed: no such column …

it’s because the app is trying to query a column that exists in the new model, but does not exist in the old local SQLite file. This is a classic schema mismatch.

Why it worked before

Locally fresh builds generate a brand-new database that matches the current model. On devices where you already had the app installed from a previous Mendix version, the old database stays and tries to reuse the old schema.

That’s why old installs suddenly fail after upgrading the Mendix runtime.

Correct solution (100% working)

You must rebuild / reset the native SQLite database on the device so it matches the new model.

Here are the supported ways to fix it:

  1. Uninstall the app from the device
    • Completely removes the old SQLite DB
    • When you reinstall, a fresh DB is created with the correct schema
  2. Enable “Encrypted Offline Database” in native build settings
    • Mendix will automatically drop and rebuild the local DB on version changes
    • This ensures no stale columns remain after upgrades
  3. Force a manual DB reset in your app
    • You can add logic to delete the local database on version mismatch (optional)

Why this matters

  • This issue only occurs in native/offline mode
  • It does not apply to web apps or online-only profiles
  • Once the database is recreated, the error disappears and retrieves work normally



answered