Fix: the Android app no longer started after the update

A build error in version 1.1 caused the Android app to hang on the launch screen after updating. Version 1.1.1 fixes this. Your data was never affected.

Version 1.1.1

The app starts again

While packaging version 1.1, a wrong variant of an internal library ended up in the Android app. Startup aborted before anything was rendered — the app stayed on the logo. Version 1.1.1 ships the correct one.

No data affected

The error occurred before any data access. Nothing was read, written or synced — everything remained intact on the server and reappears in full after the update.

What we learned

Our automated tests ran against developer builds — and the error did not occur in those. From now on the finished store build is launched and verified automatically before it reaches you.

Also fixed & improved

  • iOS was not affected by the startup issue; 1.1.1 ships there alongside Android so both platforms stay in sync.
You don't need to install any of this yourself — the web updates automatically, and the app gets the update via the store or TestFlight.

Stay in the loop

We'll send you the most important updates and tips — no spam, unsubscribe anytime.

No spam. Unsubscribe anytime. Your data stays with us.

Fix: the Android app no longer started after the update · Mokkeli Version 1.1.1 | Mokkeli