Is there an issue with the 332 apk file on fdroid?
When I upgrade through fdroid, version 332 immediately crashes on launch. When I do a fresh re-install of 332, downloaded from fdroid, version 332 crashes on launch. I've had to downgrade to 331 to make Jami work.
I created an entry in the forum on 15th June to ask if anyone else was having this problem:
Has anyone else found that Version 20220602-01 (332) for Android crashes instantly upon launch?
I’ve had to downgrade to 331.
Steps taken:
Ran upgrade within F-Droid - 332 crashed upon launch Uninstalled Installed 332 from .apk (cx.ring_332.apk) - crashed upon launch Uninstalled and downgraded to 331 using the .apk
Hardware & OS: Amazon Fire 7 (9th generation) Android 9 (I think)
Before posting a formal technical/bug report, it would be good to know if anyone else has experienced this.
So far nobody else has reported an issue.
Because the crash happens immediately upon launch, and every time, I get no option to look at the logs.
Hardware & OS:
- Amazon Fire 7 (9th generation)
- Android 9 (I think)
Steps undertaken today, 21st June:
Android settings / clear data (storage and cache) for Jami, then uninstall. Install 332 from .apk file downloaded from fdroid site (https://f-droid.org/packages/cx.ring/). Crashes on launch.
- Boot to safe mode.
- Settings / clear data (storage and cache) for Jami, then uninstall.
- Re-download .apk file from fdroid site (https://f-droid.org/packages/cx.ring/).
- Install. Immediate crash on launch.
- Settings / clear data (storage and cache) for Jami, then uninstall.
- Revert to 331 from .apk file.
- All fine.
Is there an issue with the copy of 332 on the fdroid site? Or something else? 331 is working fine on my equipment.