Skip to content
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

App crashes in start up in Android #4601

Closed
amirhosseinj1 opened this issue Mar 17, 2022 · 20 comments
Closed

App crashes in start up in Android #4601

amirhosseinj1 opened this issue Mar 17, 2022 · 20 comments
Labels
mobile:android need-to-reproduce More clues are required to reproduce the issue.

Comments

@amirhosseinj1
Copy link

What happened?

When i open the app it just shows the logseq logo and then crashes

Reproduce the Bug

  1. Open logseq (android)

Expected Behavior

No response

Screenshots

No response

Desktop Platform Information

No response

Mobile Platform Information

No response

Additional Context

No response

@andelf andelf added need-to-reproduce More clues are required to reproduce the issue. mobile:android labels Mar 18, 2022
@andelf
Copy link
Collaborator

andelf commented Mar 18, 2022

Could you provide more context:

  • os version
  • app version
  • device type

@amirhosseinj1
Copy link
Author

Could you provide more context:

  • os version
  • app version
  • device type

sure, im using huawei mate 10 lite and it has android 8 and im using logseq version 0.6.3 beta testing

@ketoxime
Copy link

I had the same problem, for me a downgrade to 0.6.2 worked just fine.

@gongxiao
Copy link

gongxiao commented Mar 26, 2022

+1, Hornor V7 Pro, Android 11, logseq 0.6.2/0.6.3/0.6.4 can not start, for me a downgrade to 0.5.9 worked just fine.

@Underknowledge
Copy link

v. 0.6.3 0.6.4 and 0.6.5 crashes when I give the storage permissions to an existing Logseq folder (syncthing <--> PC)
(I see shortly the content of my journal ~0.8 sec)

Huawei P10 VTR-L09
Android version 9
Build number 9.1.0.275

0.6.2 does not to have this issue.
Any logs I can pull to help with troubleshooting?

(my android 10 Oneplus5 is happy with v.0.6.5)

@amirhosseinj1
Copy link
Author

amirhosseinj1 commented Mar 27, 2022 via email

@pritkr
Copy link

pritkr commented Apr 13, 2022

Same
Is there anything being done to address this?

@pritkr
Copy link

pritkr commented Apr 13, 2022

Same happened to me

@gongxiao
Copy link

+1, Hornor V7 Pro, Android 11, logseq 0.6.2/0.6.3/0.6.4 can not start, for me a downgrade to 0.5.9 worked just fine.

My problem has been solved since 0.6.6.

@amirhosseinj1
Copy link
Author

+1, Hornor V7 Pro, Android 11, logseq 0.6.2/0.6.3/0.6.4 can not start, for me a downgrade to 0.5.9 worked just fine.

My problem has been solved since 0.6.6.

Unfortunately not for me

@TeebObeeT
Copy link

Hello, count me in :( Version 0.6.6 and I can't open my folder at all...

@amirhosseinj1
Copy link
Author

welcome to family 😂

@amirhosseinj1
Copy link
Author

Crash still happens in version 0.6.7

@retiarylime
Copy link

device: pocophone f1
os version: android 9
app version:

  • only 0.6.2 works fine
  • 0.6.3 until 0.6.7 crash as soon as it done parsing files

@Sun-Pengcheng
Copy link

device type: Mate 10 (Huawei)
os version: HarmonyOS 2.0.0
app version:

  • only 0.5.9 works fine
  • 0.6.0 until 0.6.7 stays on the launch screen of the app

@whuwangyong
Copy link

whuwangyong commented May 10, 2022

device type: Honor V10
os version: EMUI 8, based Android 8
app version: 0.5.5.-0.6.8

stays on the launch screen of the app。

@thiswillbeyourgithub
Copy link

thiswillbeyourgithub commented May 16, 2022

Still on 0.6.9 (Lineage OS 18.1, based on android 11)

@amirhosseinj1
Copy link
Author

amirhosseinj1 commented May 17, 2022 via email

@thiswillbeyourgithub
Copy link

Finally worked for me on 0.7.0

Similar to #4623

I then had the issue of crash when selecting the logseq folder. The workaround as described in other issues was to select the phone storage then Downloads then a new folder.

@andelf
Copy link
Collaborator

andelf commented Aug 11, 2022

This is fixed in the nightly version by #6315.
Feel free to reopen if the problem still exists.

@andelf andelf closed this as completed Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mobile:android need-to-reproduce More clues are required to reproduce the issue.
Projects
None yet
Development

No branches or pull requests