[GH-ISSUE #8159] [Bug] Appflowy_web does not update Board pages on Self-hosted server #3606

New issue

Closed

opened 2026-03-23 21:31:42 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 21:31:42 +00:00

Owner

Originally created by @aidhams on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8159

Bug Description

I just recently setup Appflowy server locally. I noticed that when I create a Board page, using the client or the web client (appflowy_web), it can create the page. But I can only update the Board page on the server using the client. Using the web client updates it locally but does not propagate the update to the server.

I have tested using Chrome and Firefox with the same result. Using the incognito mode will get the latest version of the board from the server.
Logging out and logging in again will show the locally cached version of the board page. I opened a session on Chrome and Firefox and updated each session independently, logged out and logged back in again. I got each browser's version of the Board pages but it didn't update the server because neither version appeared on the Appflowy client.
Updating the Board page from the Appflowy client updates the server but the changes are not reflected at the web client. The webclient still reads the local version of the board. Switching layout from Board to Grid and back sometimes updates the web client but it is inconsistent. Clearing the cache on Firefox does result in the server version of the Board page being displayed.
Switching from Board layout to Grid layout on the web client sometimes updates the server but the behavior is inconsistent.
It does not affect other pages. Other pages update accordingly. The Grid pages update successfully. This affects only the Board pages. The preference to read the locally cached version of the Board page and the failure to update the server version of the page will result inconsistent information.
Deleting Board pages would be reflected immediately in other browsers
Manually refreshing the page would update the server. However, changes from 2 different browsers will over write each other based on which refreshed last.
Updated the local server with 'docker compose pull' and 'git pull' to get the latest version today and no changes to the behavior.

Is there a way to disable web client temporarily and force using the client? can I just stop appflowy_web ? Or trigger a periodic refresh? The lack of update collision detection is troubling.

How to Reproduce

Create a page of type Board using either the web or client. Update the Board page using the web client / web interface. Compare the Board page using the appflowy client app.

Expected Behavior

The expected behavior is that both the web client and the client app show the same version of the Board page. Updating a board that has been updated by another user should trigger a collision warning

Operating System

Windows

AppFlowy Version(s)

Docker images with Latest tag

Screenshots

No response

Additional Context

No response

Originally created by @aidhams on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8159 ### Bug Description I just recently setup Appflowy server locally. I noticed that when I create a Board page, using the client or the web client (appflowy_web), it can create the page. But I can only update the Board page on the server using the client. Using the web client updates it locally but does not propagate the update to the server. 1. I have tested using Chrome and Firefox with the same result. Using the incognito mode will get the latest version of the board from the server. 2. Logging out and logging in again will show the locally cached version of the board page. I opened a session on Chrome and Firefox and updated each session independently, logged out and logged back in again. I got each browser's version of the Board pages but it didn't update the server because neither version appeared on the Appflowy client. 3. Updating the Board page from the Appflowy client updates the server but the changes are not reflected at the web client. The webclient still reads the local version of the board. Switching layout from Board to Grid and back sometimes updates the web client but it is inconsistent. Clearing the cache on Firefox does result in the server version of the Board page being displayed. 4. Switching from Board layout to Grid layout on the web client sometimes updates the server but the behavior is inconsistent. 5. It does not affect other pages. Other pages update accordingly. The Grid pages update successfully. This affects only the Board pages. The preference to read the locally cached version of the Board page and the failure to update the server version of the page will result inconsistent information. 6. Deleting Board pages would be reflected immediately in other browsers 7. Manually refreshing the page would update the server. However, changes from 2 different browsers will over write each other based on which refreshed last. Updated the local server with 'docker compose pull' and 'git pull' to get the latest version today and no changes to the behavior. Is there a way to disable web client temporarily and force using the client? can I just stop appflowy_web ? Or trigger a periodic refresh? The lack of update collision detection is troubling. ### How to Reproduce Create a page of type Board using either the web or client. Update the Board page using the web client / web interface. Compare the Board page using the appflowy client app. ### Expected Behavior The expected behavior is that both the web client and the client app show the same version of the Board page. Updating a board that has been updated by another user should trigger a collision warning ### Operating System Windows ### AppFlowy Version(s) Docker images with Latest tag ### Screenshots _No response_ ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:31:42 +00:00

mirror commented

2026-03-23 21:31:42 +00:00

Author

Owner

@khorshuheng commented on GitHub (Aug 8, 2025):

Some clarification:

AppFlowy Web currently doesn't support real time UI refresh yet (it will be implemented soon). So browser refresh is required to see the latest changes - changes from desktop doesn't immediately reflect on the web.
AppFlowy Web send updates to the server when you stop typing, rather than on refresh.
There are issues with desktop/mobile client when board is concern, for certain updates like moving cards on board. Even if it the update is from another desktop client, the UI is not refreshed immediately.

@khorshuheng commented on GitHub (Aug 8, 2025): Some clarification: 1. AppFlowy Web currently doesn't support real time UI refresh yet (it will be implemented soon). So browser refresh is required to see the latest changes - changes from desktop doesn't immediately reflect on the web. 2. AppFlowy Web send updates to the server when you stop typing, rather than on refresh. 3. There are issues with desktop/mobile client when board is concern, for certain updates like moving cards on board. Even if it the update is from another desktop client, the UI is not refreshed immediately.

mirror commented

2026-03-23 21:31:43 +00:00

Author

Owner

@annieappflowy commented on GitHub (Aug 15, 2025):

AppFlowy Web now supports real time sync. @aidhams , I'm closing the issue for now.

@annieappflowy commented on GitHub (Aug 15, 2025): AppFlowy Web now supports real time sync. @aidhams , I'm closing the issue for now.

mirror referenced this issue

2026-03-23 22:20:18 +00:00

[PR #3606] [MERGED] Fix updated the image to use Image Image.file instead of FileImage, because it wasn't working for macOs #5787