[Bug] Server DB Mode: Critical UI/State sync bugs on Mobile Web view and the new Native App (Released around April 2026)

Client Type

Mobile App (React Native), Web (Mobile Browser)

Operating System

Android

Deployment Platform

Self hosting Docker

Version

2.2

Browser

Chrome

What happened?

Bug 1 (Mobile Web View): Custom agents created on the desktop client or desktop web interface are completely invisible when logging into the same account via a mobile browser using the default narrow-screen layout.

Bug 2 (New Native App): The messaging engine for custom agents completely freezes and stops responding after the App is resumed from the background. Tap into the newly created custom agent, type a message, and click the send button yields no response.

Bug 3 (New Native App): Modifying the metadata (e.g., name or avatar) of an agent inside the Native App yields no immediate visual feedback on the screen. The UI remains unchanged, continuously displaying the old name and avatar snapshot.

How to reproduce it?

For Bug 1:

Create a custom agent on the Desktop Web interface.

Log into the same account using a mobile browser (e.g., Chrome on Android) without enabling desktop mode. Observe that the custom agent list is empty.

Toggle the mobile browser setting to "Request Desktop Site" (Desktop View). The page re-renders, and the custom agent list instantly appears and functions normally.

For Bug 2:

Open the new Native App, create a new custom agent, select a model, and send a message. The chat functions normally, and the message histories instantly sync to the PostgreSQL backend and appear on the Desktop Web interface.

Force-close the App or send it to the background, then reopen it.

Tap into the newly created custom agent, type a message, and click the send button. The button is completely unresponsive; no network request is sent, and no records are updated in the backend database or visible on other clients. (Note: System-default agents or empty conversations are unaffected by this bug).

For Bug 3:

While the App is running, open an agent's settings and change its name or avatar, then tap save.

The UI remains unchanged, continuously displaying the old name and avatar snapshot.

Force-close the App and reopen it. The name and avatar are now successfully updated in the UI. Checking the Desktop Web or Windows client confirms the changes were successfully pushed to the PostgreSQL database during step 1.

What it should be?

For Bug 1: The mobile viewport layout should trigger the same initialization hooks to fetch and render the full cloud custom agent array (api/agent/list) as the desktop layout does, ensuring multi-device data parity.

For Bug 2: When the App enters the onResume or wake-up lifecycle state, it should successfully re-bind and re-activate the cloud session_id/UUID within the Chat Store runtime state so that the chat message handler can route outbound messages properly.

For Bug 3: Upon receiving a successful asynchronous response (200 OK) from the metadata mutation API (PATCH /api/agent/update), the App should instantly trigger a state invalidation or UI re-render signal to update the view on the screen.

Additional Information

Regarding Bug 1: Since switching to "Desktop View" on the same device instantly resolves the issue, the backend database, API routing, and reverse proxy layers are verified to be fully functional. The bug is isolated to the initialization lifecycle fetching logic inside the mobile responsive view component.

Regarding Bug 2: The outbound messaging works flawlessly upon agent creation, indicating that the API credentials and network paths are intact. The failure occurs only during the session resumption state, where the front-end code silently drops the click event because it fails to establish a valid active session target for custom cloud agents.

Regarding Bug 3: This behavior confirms that the App's data-writing channel (RESTful API) works perfectly. The bug is strictly confined to the front-end UI layer of the Native App, where the view controller components fail to listen to or execute the refresh state after a successful network modification.

️ Willing to Submit a PR?

None

✅ Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a LobeChat issue and not a third-party library or provider issue.
• Check that this is a concrete bug. For Q&A, please use GitHub Discussions or join our Discord Server.