Replies don’t come through
There’s also no way to send bug reports on this app
This app definitely has its issues which would be understandable if it wasn’t a paid application.
Response from developer
Thank you for describing this so precisely. It was a real bug: when you left the app or locked the phone, iOS suspended it and the reply in progress was lost, even though your server had finished it. The next update, 1.11, fixes it. If the reply is cut off while you are away, the app asks again as soon as you come back, and the full answer appears in the same place. On bug reports: Settings › Diagnostics › Report a bug opens an email with the last hour of the app's log, and you can read everything before sending. Sorry for the trouble, and thanks for sticking with the app.
Great start
Response from developer
Thank you! You were right: one piece of text, in the message box, had no translation, so the app fell back to Portuguese there. This was fixed in version 1.9, together with a check that catches any untranslated text before a release. If you still see Portuguese anywhere on the current version, please let me know where and I will fix it.
default mml
Response from developer
Vielen Dank für das Feedback — der Punkt ist berechtigt. Ab der nächsten Version merkt sich die App das zuletzt gewählte Modell, sodass jeder neue Chat direkt damit startet. Ein erneutes Auswählen ist dann nicht mehr nötig.
Great app!
Response from developer
Thank you! The quirks you spotted were the relative timestamps in the chat list — they were pinned to Portuguese instead of following the app's language. Fixed in the next version. Glad the themes are working for you!
Leider (noch) nicht zu gebrauchen.
Response from developer
Thank you for the detailed report — both problems were real bugs on our side, and both are fixed in version 1.5, which is on its way to the App Store. Missing replies: Open WebUI 0.10 changed how it stores assistant messages. The text now lives in a new structured field, and the app was still reading only the old one, so anything generated in the browser appeared blank. Worse, continuing that conversation from the phone could overwrite it on the server. The app now reads the new format, and when it saves it only appends — it never rewrites what the server already has. An open chat also refreshes on its own, so replies written in the browser show up without you leaving the screen. Web search: the app was sending the old "web search" flag, which newer Open WebUI versions ignore for API clients, so nothing was ever searched. The app now runs the search through your server's own search endpoint — the same one the web interface uses — and shows the sources it used. If the server's search engine itself fails, the app now tells you instead of letting the model answer "I have no internet access". Could you tell me which search engine is configured? And if you noticed anything else that felt off, I would really like to hear it — this is a small project, and reports like yours are what make it better.
