[GH-ISSUE #2001] [Bug] Deleting a referenced board results in a permanent CircularProgressIndicator. #788

Closed
opened 2026-03-23 20:41:04 +00:00 by mirror · 7 comments
Owner

Originally created by @a-wallen on GitHub (Mar 15, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2001

Originally assigned to: @sshdopey on GitHub.

Bug Description

If you add a referenced board to a page and delete the board, the page will have a permanent circular progress indicator.

How to Reproduce

  1. Create a new board.
  2. Reference the board inside of a page.
  3. Delete the board that you created earlier.
  4. Close the app.
  5. Open the app.
  6. Open the page where you added the referenced board. There will be a circular progress indicator that you cannot remove.

Expected Behavior

The referenced board should not show.

Operating System

Windows 10

AppFlowy Version(s)

main

Screenshots

image

Additional Context

No response

Originally created by @a-wallen on GitHub (Mar 15, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2001 Originally assigned to: @sshdopey on GitHub. ### Bug Description If you add a referenced board to a page and delete the board, the page will have a permanent circular progress indicator. ### How to Reproduce 1. Create a new board. 2. Reference the board inside of a page. 3. Delete the board that you created earlier. 4. Close the app. 5. Open the app. 6. Open the page where you added the referenced board. There will be a circular progress indicator that you cannot remove. ### Expected Behavior The referenced board should not show. ### Operating System Windows 10 ### AppFlowy Version(s) main ### Screenshots ![image](https://user-images.githubusercontent.com/44445638/225464314-768c7693-81b8-4df0-a6d8-c421279b9508.png) ### Additional Context _No response_
Author
Owner

@sshdopey commented on GitHub (Mar 15, 2023):

I have reproduced this bug, and would like this task to be assigned to me.

<!-- gh-comment-id:1470973747 --> @sshdopey commented on GitHub (Mar 15, 2023): I have reproduced this bug, and would like this task to be assigned to me.
Author
Owner

@sshdopey commented on GitHub (Mar 15, 2023):

just checked and the bug doesn't only exist with boards but with grids as well

<!-- gh-comment-id:1470976451 --> @sshdopey commented on GitHub (Mar 15, 2023): just checked and the bug doesn't only exist with boards but with grids as well
Author
Owner

@a-wallen commented on GitHub (Mar 15, 2023):

@DestinedCodes, thank you!

<!-- gh-comment-id:1470983271 --> @a-wallen commented on GitHub (Mar 15, 2023): @DestinedCodes, thank you!
Author
Owner

@sshdopey commented on GitHub (Mar 15, 2023):

I just began working on it. I'll keep this space posted on my progress. I am applying for octernship, so an issue with the label "good first issue for devs" would be great.😊😊😊

<!-- gh-comment-id:1470989163 --> @sshdopey commented on GitHub (Mar 15, 2023): I just began working on it. I'll keep this space posted on my progress. I am applying for octernship, so an issue with the label "good first issue for devs" would be great.😊😊😊
Author
Owner

@a-wallen commented on GitHub (Mar 16, 2023):

I suspect the answer is in built_in_page_widget.dart

  @override
  Widget build(BuildContext context) {
    return FutureBuilder<dartz.Either<ViewPB, FlowyError>>(
      builder: (context, snapshot) {
        if (snapshot.hasData) {
          final board = snapshot.data?.getLeftOrNull<ViewPB>();
          if (board != null) {
            return _build(context, board);
          }
        }
        return const Center(
          child: CircularProgressIndicator(),
        );
      },
      future: AppBackendService().getView(appID, gridID),
    );
  }

<!-- gh-comment-id:1471111319 --> @a-wallen commented on GitHub (Mar 16, 2023): I suspect the answer is in `built_in_page_widget.dart` ```dart @override Widget build(BuildContext context) { return FutureBuilder<dartz.Either<ViewPB, FlowyError>>( builder: (context, snapshot) { if (snapshot.hasData) { final board = snapshot.data?.getLeftOrNull<ViewPB>(); if (board != null) { return _build(context, board); } } return const Center( child: CircularProgressIndicator(), ); }, future: AppBackendService().getView(appID, gridID), ); } ```
Author
Owner

@sshdopey commented on GitHub (Mar 17, 2023):

I have fixed the bug. please review😊. It was interesting working on this, but it wasn't really easy to build the app on my laptop. (I had to do more debugging on my laptop than I had to fix the code 😂)

<!-- gh-comment-id:1473385980 --> @sshdopey commented on GitHub (Mar 17, 2023): I have fixed the bug. please review😊. It was interesting working on this, but it wasn't really easy to build the app on my laptop. (I had to do more debugging on my laptop than I had to fix the code 😂)
Author
Owner

@annieappflowy commented on GitHub (Aug 11, 2023):

Fixed

<!-- gh-comment-id:1674205384 --> @annieappflowy commented on GitHub (Aug 11, 2023): Fixed
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#788
No description provided.