mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #7176] [Bug] Windows and Android Apps Fail to Launch #3177
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hipomedrus on GitHub (Jan 8, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7176
Originally assigned to: @LucasXu0, @asjqkkkk on GitHub.
Bug Description
The Windows app and also Android app of AppFlowly doesn't start.
How to Reproduce
I am not sure but I guess this happened after I opened and tried to edit some pages on Android app and also on the Windows app at the same time without waiting for sync. But I am not sure whether this was the reason behind the bug or not.
Expected Behavior
Launch of the Windows app and launch of the Android app without any problems
Operating System
Windows 11
Android 14
AppFlowy Version(s)
all versions from v0.7.3 to v0.8.0
Screenshots
No response
Additional Context
Uninstalling and reinstalling didn't work. I also tried with another account but the application still failed to launch.
@asjqkkkk commented on GitHub (Jan 9, 2025):
Hi @hipomedrus , this issue is similar to #6979
Have you tried to delete the folder related to appflowy?
such as :
[C:\Users\username\AppData\Roaming\io.appflowy (%AppData%/io.appflowy)]
or [C:\Users[Username]\AppData\Local\Temp\appflowy_flutter...]
@hipomedrus commented on GitHub (Jan 9, 2025):
I tried but it didn't work. With deleting that folder making a fresh install, app started with sign-in screen bu after I completed my sign-in from e-mail, the app crashed again without any error code. Now it is same as before.
Also I am sorry, I forget to mention but Android app acts same. When I try to sign-in on the Android app, it crashes and I can't launch it again. I think whole problem is related with my account. Because I can use both without sign-in.
Edit: I edited the title and the details in issue
@asjqkkkk commented on GitHub (Jan 10, 2025):
Hi @hipomedrus , can you share your log files. Here's the guide on how to export them: https://appflowy.com/ccf3ca5a-7ecd-4c35-805c-3a3c9c22e87d/AppFlowy-Q-A
@hipomedrus commented on GitHub (Jan 11, 2025):
Sure @asjqkkkk, here it is: appflowy_logs.zip
@asjqkkkk commented on GitHub (Jan 14, 2025):
Thank you for the logs files, we will see if we can find the issue based on them.
@annieappflowy commented on GitHub (Feb 23, 2025):
What's the status / conclusion on this issue?
@asjqkkkk commented on GitHub (Feb 24, 2025):
We can't find critical information in the log files, perhaps we need to add more print statements to our code, which will take a lot of time to verify, and we haven't started to do this yet.
Additionally, there is a potential problem with the user account, and I'm not sure if it's associated with the cloud.