-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing On Android #4993
Comments
Yes its my problem too |
@amirhosseinj1 @JakesCodingLab442 Can you confirm the permission settings? |
Yes, it's already have all the permissions. the problem starts when i wanna open a graph, app load up normally but when i wanna open up a folder aka graph it just crashes. the problem started after version 0.6.2. 0.6.2 works fine. @cnrpman |
This is happening with me as well. I'm not sure what's the cause. It was working fine before I imported my notes folder from my desktop. My first impression was that it was happening because of reserved characters in file names (commas, inverted commas, dots, slashes, $, @, ":") so I removed all of those and re-imported the folder. It still crashed. The folder is stored in the android home folder |
I've deleted the |
I wonder if it may have been caused by an OS upgrade? When I first imported my vault I was running Android 11, these crashes took place when I re-imported the folder, by which time I had upraded to Android 12. |
This behavior occurs on the nightly version of the app, as well as 0.6.2, and 0.6.6. |
I made an attempt to fish out the error message using logcat:
|
This issue is probably a duplicate of #3789 |
This is fixed in the nightly version by #6315. |
What happened?
Opening a directory or creating a new one crashes the app. Has been a problem since 0.6.3 Running android 9 on Galaxy A8
Reproduce the Bug
Expected Behavior
Crashes the app
Screenshots
No response
Desktop Platform Information
No response
Mobile Platform Information
Device: Samsung Galaxy A8
Version: Android 9
Logseq Version: 0.6.6
Additional Context
No response
The text was updated successfully, but these errors were encountered: