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.
