Skip to main content

Uni-Verein 1.8.4 – No More Blank Screens, Mail Works Again on iPhone 📱🛟

· 2 min read
René Herrmann
René Herrmann
Senior developer

Published on October 3, 2026

On the same day as 1.8.3 comes Uni-Verein 1.8.4, a small bug-fix release: sending mail works on the iPhone again, and if a page ever fails to load, the app stays usable from now on.

Highlights​

  • 📱 Mail works on the iPhone again: Opening "Mail" no longer shows a blank white screen
  • 🛟 No more blank screens after errors: If a page fails to load, you now see an error message with a reload button. The navigation stays usable, so you can switch to another page
  • 🔄 Smoother updates: If the app is open while a new version is deployed, it reloads once on its own instead of failing to open a page

Fixes​

  • 📱 Mail on iPhone (UV-51): Opening "Mail" on an iPhone no longer shows a blank white screen. The mail editor was accessed after it had already been closed, and the resulting error took down the whole app
  • 🛟 Error message instead of a blank screen: If a page runs into an error, an error message ("Hier ist etwas schiefgelaufen") with the buttons "Erneut versuchen" and "Neu laden" now appears in the content area. The sidebar and the mobile bottom navigation keep working, and switching to another page clears the error
  • 🔄 Missing page files after an update: If the app was still open from the previous version and a page file of that version no longer exists, the app now reloads once and loads the current version. If the file is still missing after that, the error message appears instead of reloading again and again

⚠️ Upgrade Notes​

  • Always update with docker-compose-update.yml, as described in the README
  • No database migration is needed
  • No changes to your settings or the API are needed

Why These Updates Matter​

A blank screen is the worst feedback for users: you don't know what happened or what to do next. With the error message and the navigation staying usable, everyone can carry on even after an unexpected error, and the automatic reload after updates prevents many such cases in the first place.

What's Next?​

Real-world feedback is, as always, very welcome via GitHub Issues. Check back here again soon!