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

Joplin not opening but immediately crashing in Android 4.3 & 4.4 #4507

Closed
jdofo opened this issue Feb 9, 2021 · 3 comments
Closed

Joplin not opening but immediately crashing in Android 4.3 & 4.4 #4507

jdofo opened this issue Feb 9, 2021 · 3 comments
Labels
bug It's a bug stale An issue that hasn't been active for a while...

Comments

@jdofo
Copy link

jdofo commented Feb 9, 2021

First of all, thank you very much for such interesting and potential replacement of Evernote :)

Last time I installed Joplin app (probably around summer 2020) in my Android 4.3 and 4.4 mobile phones, it was working fine.

However, I decided to update Joplin few days ago (planning to sync my computer and phones through "file sync" + Syncthing) but, unfortunately, it doesn't work anymore in none of my phones. After installing latest update, it simply doesn't allow me to even open the app: the screen gets white but after a while, there is a "CTD" message - "Joplin application stopped unexpectedly". I tried to uninstall and install from scratch several times, but encountering the same crashing behaviour.

I know these are nowadays considered "old" mobile phones, but Joplin app specifies as requirement: "Android 4.1 and newer versions". Is planned obsolescence also arriving to open-source and free software? If so, future is becoming even darker...

Thank you very much in advance! Cheers

@philip-n
Copy link
Contributor

philip-n commented Feb 22, 2021

Came here for the same reason. This seems to be a known bug in an underlying component that Joplin uses (and that component might incorrectly have claimed it still supports 4.1 while in fact it does not), see #4057

So I guess that there will be no fix, unfortunately. I just opened #4585 to prevent other users from falling in the same trap. Assuming that there are other people who still use Android 4.x, that is 🙂

@stale
Copy link

stale bot commented Mar 26, 2021

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale An issue that hasn't been active for a while... label Mar 26, 2021
@stale
Copy link

stale bot commented Jun 3, 2021

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

2 participants