AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 04:46:56 +00:00

[GH-ISSUE #6292] [Bug] crashed on Windows 11, runs as background process but not as app #2780

New issue

Closed

opened 2026-03-23 21:25:05 +00:00 by mirror · 7 comments

mirror commented

2026-03-23 21:25:05 +00:00

Owner

Originally created by @billybillymc on GitHub (Sep 13, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6292

Bug Description

My computer just froze up and when I got it back on and reopened everything only AppFlowy refused to reopen.

How to Reproduce

It appears that Appflowy (without any action on my part) crashed my computer and now refuses to let me in. I can see AppFlowy running as a background process and accessing location data on Windows 11, but it is not loading the GUI on the machine where it crashed. I was able to load my locally hosted data from another machine, so the issue is not the locally saved data. I have uninstalled and reinstalled AppFlowy on this machine many times now and it won't open. I have also reinstalled Windows and done multiple system restarts.

Expected Behavior

AppFlowy to open as an app.

Operating System

Windows 11

AppFlowy Version(s)

0.6.7, 0.6.7.2, 0.6.8, 0.6.9, 0.6.5, 0.6.6 (I have tried uninstalling and reinstalling many times and the issue has persisted through these installations since the initial crash)

Screenshots

No response

Additional Context

No response

Originally created by @billybillymc on GitHub (Sep 13, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6292 ### Bug Description My computer just froze up and when I got it back on and reopened everything only AppFlowy refused to reopen. ### How to Reproduce It appears that Appflowy (without any action on my part) crashed my computer and now refuses to let me in. I can see AppFlowy running as a background process and accessing location data on Windows 11, but it is not loading the GUI on the machine where it crashed. I was able to load my locally hosted data from another machine, so the issue is not the locally saved data. I have uninstalled and reinstalled AppFlowy on this machine many times now and it won't open. I have also reinstalled Windows and done multiple system restarts. ### Expected Behavior AppFlowy to open as an app. ### Operating System Windows 11 ### AppFlowy Version(s) 0.6.7, 0.6.7.2, 0.6.8, 0.6.9, 0.6.5, 0.6.6 (I have tried uninstalling and reinstalling many times and the issue has persisted through these installations since the initial crash) ### Screenshots _No response_ ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:25:05 +00:00

mirror commented

2026-03-23 21:25:06 +00:00

Author

Owner

@LucasXu0 commented on GitHub (Sep 13, 2024):

Hi, @billybillymc. Were you using AppFlowy Cloud or Local mode before your computer froze up?

@LucasXu0 commented on GitHub (Sep 13, 2024): Hi, @billybillymc. Were you using AppFlowy Cloud or Local mode before your computer froze up?

mirror commented

2026-03-23 21:25:06 +00:00

Author

Owner

@billybillymc commented on GitHub (Sep 13, 2024):

Hi, @billybillymc. Were you using AppFlowy Cloud or Local mode before your computer froze up?

I was using local mode when my computer froze up. As an update, I've done a Windows reinstall and multiple system restarts since the issue began too. No luck with any of it.

@billybillymc commented on GitHub (Sep 13, 2024): > Hi, @billybillymc. Were you using AppFlowy Cloud or Local mode before your computer froze up? I was using local mode when my computer froze up. As an update, I've done a Windows reinstall and multiple system restarts since the issue began too. No luck with any of it.

mirror commented

2026-03-23 21:25:06 +00:00

Author

Owner

@LucasXu0 commented on GitHub (Sep 13, 2024):

If you were using local mode, please do not delete the local folder unless you have backed up your data.

Would you mind launching AppFlowy from CMD and posting the result?

Open the Command Prompt program.
Execute the following command

"C:\Program Files (x86)\AppFlowy\AppFlowy.exe"

@LucasXu0 commented on GitHub (Sep 13, 2024): If you were using local mode, please do not delete the local folder unless you have backed up your data. Would you mind launching AppFlowy from CMD and posting the result? - Open the Command Prompt program. - Execute the following command ``` "C:\Program Files (x86)\AppFlowy\AppFlowy.exe" ```

mirror commented

2026-03-23 21:25:07 +00:00

Author

Owner

@billybillymc commented on GitHub (Sep 13, 2024):

I have my local folder saved.

I have executed the command from CMD. Same result: AppFlowy appears as a background process and initiates contact with my location data but does not launch as a foreground app as I see happening on the machine where it is still working.

@billybillymc commented on GitHub (Sep 13, 2024): I have my local folder saved. I have executed the command from CMD. Same result: AppFlowy appears as a background process and initiates contact with my location data but does not launch as a foreground app as I see happening on the machine where it is still working.

mirror commented

2026-03-23 21:25:07 +00:00

Author

Owner

@billybillymc commented on GitHub (Sep 13, 2024):

This issue has been resolved. The uninstallation executable doesn't remove the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not sure what exactly inside the settings/cache in there was causing this specific bug but after deleting that folder I was able to get AppFlowy.exe to launch as an app and not just a background process. Thank you very much @LucasXu0 for replying!

@billybillymc commented on GitHub (Sep 13, 2024): This issue has been resolved. The uninstallation executable doesn't remove the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not sure what exactly inside the settings/cache in there was causing this specific bug but after deleting that folder I was able to get AppFlowy.exe to launch as an app and not just a background process. Thank you very much @LucasXu0 for replying!

mirror commented

2026-03-23 21:25:07 +00:00

Author

Owner

@LucasXu0 commented on GitHub (Sep 13, 2024):

This issue has been resolved. The uninstallation executable doesn't remove the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not sure what exactly inside the settings/cache in there was causing this specific bug but after deleting that folder I was able to get AppFlowy.exe to launch as an app and not just a background process. Thank you very much @LucasXu0 for replying!

We didn't remove this path before because it contains user data. If the user accidentally uninstalls our app while using local mode, all the data would be cleared. Let me see if we can set a configuration in the uninstall program to allow the user to clear the data if they toggle the configuration.

@LucasXu0 commented on GitHub (Sep 13, 2024): > This issue has been resolved. The uninstallation executable doesn't remove the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not sure what exactly inside the settings/cache in there was causing this specific bug but after deleting that folder I was able to get AppFlowy.exe to launch as an app and not just a background process. Thank you very much @LucasXu0 for replying! We didn't remove this path before because it contains user data. If the user accidentally uninstalls our app while using local mode, all the data would be cleared. Let me see if we can set a configuration in the uninstall program to allow the user to clear the data if they toggle the configuration.

mirror commented

2026-03-23 21:25:07 +00:00

Author

Owner

@billybillymc commented on GitHub (Sep 13, 2024):

That makes sense! I think the more primary issue may be whatever caused
that kernel event. I would suppose that whatever was in the AppRoaming that
caused that event led Microsoft to prevent AppFlowy from launching as an
app and kept it confined to background process status. Let me know if you'd
like to look at the specific files I had in AppRoaming at the time that the
issue persisted!

On Fri, Sep 13, 2024 at 1:41 AM Lucas @.***> wrote:

This issue has been resolved. The uninstallation executable doesn't remove
the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not
sure what exactly inside the settings/cache in there was causing this
specific bug but after deleting that folder I was able to get AppFlowy.exe
to launch as an app and not just a background process. Thank you very much
@LucasXu0 https://github.com/LucasXu0 for replying!

We didn't remove this path before because it contains user data. If the
user accidentally uninstalls our app while using local mode, all the data
would be cleared. Let me see if we can set a configuration in the uninstall
program to allow the user to clear the data if they toggle the
configuration.

—
Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/6292#issuecomment-2348075218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6QNYG3U3ZFIKXMIPJXMLLZWJ3JXAVCNFSM6AAAAABOEPM2WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGA3TKMRRHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

@billybillymc commented on GitHub (Sep 13, 2024): That makes sense! I think the more primary issue may be whatever caused that kernel event. I would suppose that whatever was in the AppRoaming that caused that event led Microsoft to prevent AppFlowy from launching as an app and kept it confined to background process status. Let me know if you'd like to look at the specific files I had in AppRoaming at the time that the issue persisted! On Fri, Sep 13, 2024 at 1:41 AM Lucas ***@***.***> wrote: > This issue has been resolved. The uninstallation executable doesn't remove > the settings in C:/Users/{username}/AppData/Roaming/io.appflowy. I'm not > sure what exactly inside the settings/cache in there was causing this > specific bug but after deleting that folder I was able to get AppFlowy.exe > to launch as an app and not just a background process. Thank you very much > @LucasXu0 <https://github.com/LucasXu0> for replying! > > We didn't remove this path before because it contains user data. If the > user accidentally uninstalls our app while using local mode, all the data > would be cleared. Let me see if we can set a configuration in the uninstall > program to allow the user to clear the data if they toggle the > configuration. > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/6292#issuecomment-2348075218>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AC6QNYG3U3ZFIKXMIPJXMLLZWJ3JXAVCNFSM6AAAAABOEPM2WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGA3TKMRRHA> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >

mirror referenced this issue

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

[PR #2780] [MERGED] test: add integration test for importing multiple markdowns #5421