openwebui 0.57 Can't use image Q&A on mobile.

[daxiass]

Bug Report

Important Notes

• Before submitting a bug report: Please check the Issues or Discussions section to see if a similar issue or feature request has already been posted. It's likely we're already tracking it! If you’re unsure, start a discussion post first. This will help us efficiently focus on improving the project.

• Collaborate respectfully: We value a constructive attitude, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We’re here to help if you’re open to learning and communicating positively. Remember, Open WebUI is a volunteer-driven project managed by a single maintainer and supported by contributors who also have full-time jobs. We appreciate your time and ask that you respect ours.

• Contributing: If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI.

• Bug reproducibility: If a bug cannot be reproduced with a :main or :dev Docker setup, or a pip install with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "issues" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help!

Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!

---

Installation Method

[docker]

Environment

• Open WebUI Version: [0.57]

• Ollama (if applicable): [It's not enabled.]

• Operating System: [ios18.2 android13]

• Browser (if applicable): [System default browser ]

Confirmation:

• [1] I have read and followed all the instructions provided in the README.md.
• [1] I am on the latest version of both Open WebUI and Ollama.
• [no] I have included the browser console logs.
• [no] I have included the Docker container logs.
• [1] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

[I want to be able to use image Q&A on my phone.]

Actual Behavior:

[I've tested on all my devices, and even had friends test, but none of our phones can use image-based Q&A. We have fast internet, and the images are small, so there's no issue with uploading. However, image-based Q&A works fine on the desktop website.]

Description

Bug Summary:
[openwebui 0.57 Can't use image Q&A on mobile.]

Reproduction Details

Steps to Reproduce:
[On mobile, the image Q&A process fails as follows:

1. I open the website on my phone.
2. I upload an image and type my question.
3. I send the question.
   Result: The system freezes. If I close and reopen OpenWebUI, the entire conversation thread is gone.]

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots/Screen Recordings (if applicable):
The mobile app keeps freezing：

The desktop version works fine：

Additional Information

[I think I've found the key issue. It seems the free Gemini API might be causing the problem. Due to high usage, it likely returns a 429 error. On mobile, when a 429 error occurs, the app freezes and doesn't display an error message, and the conversation thread disappears. On desktop, when a 429 error happens, it shows an error message, and I can manually click to regenerate the response.

This 429 issue is also strange. OpenWebUI seems prone to 429 errors with Gemini, while I haven't encountered a single 429 error with Cherry Studio. (I'm not sure if the Cherry Studio author has optimized for 429 errors by automatically retrying failed requests, so I don't have to manually click to regenerate.I'm guessing its author specifically optimized for this situation and just didn't display it on the front end.)

It's this specific 429 error：

]

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

[pesschap]

Did you managed to solve this?