Logseq Android App crashes since Versoin 0.10.6

My Logseq Android App crashes since Versoin 0.10.6
I just updated to 0.10.7 and have the same issue still.

I use Logseq Sync.

A Github Post about 0.10.6 is here:

Otherwise not many people seem to have the same issue, for i didn´t find any other post about it.

Greetings

Have you tried the usual things like clearing cache and data of the app? I know it doesn’t help you but at least for me the Android 0.10.6. Works fine both on a phone and a tablet. So I suspect something on your phone

Knowing that it works for you does help. I also tried everything you said and the app worked for as long as i didn’t try to sync. As soon as i logged in my Graph it wanted to sync and then it crashed.

I didn’t realise your issue seems related to sync. I don’t use Logseq sync so this may be why it works for me

Definitly seems to be a syncing issue. I tried several older android versions and they all crash as soon as try to sync.

Update: I too was a victim of the already known special-character-in-page-name error. After going through all my pages (which are a lot) i found one that seem to have caused the crash with having “It’s” in filename.

Which are the illegal characters, so I can look for them too? Mine keeps crashing all the time since I joined Logseq Sync

1 Like

This issue has made LogSeq unusable for me on my phone. I’ve deleted all the special characters used in the titles of my pages, and still it crashes.

It would be useful to know exactly which special characters cause the crash

1 Like

I don’t really recall what character caused my crash. Most likely " 's" as in “what’s up” or something like that.

I know it’s been a while since anyone posted here but I am having the same issue on my Android phone. After I sync, Logseq crashes. I have to go to Settings, Apps, Logseq, Storage, and clear cache and clear data. Then when I reopen Logseq, I have to select my target folder again and let it go through the parsing of files process, only to crash again after the next sync.
Regarding the ‘special character’ issue mentioned in the above string, could an underscore in a file name be considered a special character? I have several of those. Thanks a lot.

The underscore is a “legal” character. You can find all troublesome characters in the technical documentation (CC @Will_Coombe—sorry for the late reply):

https://docs.logseq.com/#/page/logseq%20file%20and%20folder%20naming%20rules

1 Like

Thank you, I will have a look.