[GH-ISSUE #7783] [Bug] UI refresh issue when dragging block under one heading to another #3432

Open
opened 2026-03-23 21:30:06 +00:00 by mirror · 2 comments
Owner

Originally created by @khorshuheng on GitHub (Apr 19, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7783

Originally assigned to: @appflowy on GitHub.

Bug Description

When dragging a checkbox under one heading to another, the update isn't reflected on another device that is editing the same document, until the device navigate to another page and come back, forcing a UI refresh.

How to Reproduce

Have two devices editing the same document. On the first device, create two Headings. On the first heading, add a checkbox. Wait until the other device detects the change.

Then, on the first device, move the checkbox from the first heading to the second heading. The second device does not detect this change. Even though subsequent updates did get send to the device.

The change does indeed sync to the server - we can see the latest update on the web version at all time. If the second device navigate to another document, then come back, the content will also be updated.

EDITED - seems like this is applicable for other type of blocks as well, not just checkbox

Expected Behavior

Updates should be reflected on all devices.

Operating System

Linux

AppFlowy Version(s)

0.8.8

Screenshots

Image

Additional Context

This is first reported by a self hoster on discord: https://discordapp.com/channels/903549834160635914/903553722804748309/1362967886603358329

Originally created by @khorshuheng on GitHub (Apr 19, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7783 Originally assigned to: @appflowy on GitHub. ### Bug Description When dragging a checkbox under one heading to another, the update isn't reflected on another device that is editing the same document, until the device navigate to another page and come back, forcing a UI refresh. ### How to Reproduce Have two devices editing the same document. On the first device, create two Headings. On the first heading, add a checkbox. Wait until the other device detects the change. Then, on the first device, move the checkbox from the first heading to the second heading. The second device does not detect this change. Even though subsequent updates did get send to the device. The change does indeed sync to the server - we can see the latest update on the web version at all time. If the second device navigate to another document, then come back, the content will also be updated. EDITED - seems like this is applicable for other type of blocks as well, not just checkbox ### Expected Behavior Updates should be reflected on all devices. ### Operating System Linux ### AppFlowy Version(s) 0.8.8 ### Screenshots ![Image](https://github.com/user-attachments/assets/1a0529ba-334a-4779-9d26-e023c2a35be1) ### Additional Context This is first reported by a self hoster on discord: https://discordapp.com/channels/903549834160635914/903553722804748309/1362967886603358329
Author
Owner

@larsenv commented on GitHub (Apr 19, 2025):

Please provide screenshots / additional context

<!-- gh-comment-id:2816485081 --> @larsenv commented on GitHub (Apr 19, 2025): Please provide screenshots / additional context
Author
Owner

@bruari commented on GitHub (Apr 24, 2025):

Bug Demo Video

See the above demo video. These are recorded in near real-time sync. User1 is performing the data entry. User1 and User2 are on two different accounts signed into the latest macOS Desktop Client. Our self-hosted containers are recently fully updated. Let us know if any other information is needed or any questions. Thanks!

<!-- gh-comment-id:2828844354 --> @bruari commented on GitHub (Apr 24, 2025): ![Bug Demo Video](https://tx.moeny.ai:8490/d3siS0xE0f/combined_demo.gif) See the above demo video. These are recorded in near real-time sync. User1 is performing the data entry. User1 and User2 are on two different accounts signed into the latest macOS Desktop Client. Our self-hosted containers are recently fully updated. Let us know if any other information is needed or any questions. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#3432
No description provided.