-
Notifications
You must be signed in to change notification settings - Fork 676
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
Element crashes in loop after initial sync #1709
Comments
I'm debating myself should I make new bug or add to this.. Exact same crash happends on 1.0.0 googleplay version too, Device is Cosmo Communicator, Android 9. After updating working Riot.imX to element it just crashess on startup, and clearing all cache and storage does not help, it keeps crashing after login and some sync.. |
I'm happy to gather logs via other ways, I just don't know how |
I was able to send a rageshake :) |
I had issues with v1 but updating to element-dbg 1.0.1 solved it. |
Should be fixed in next release, it's a proguard/realm issue. Thanks for pointing! |
It just brings a popup "Element (Riot.im) keeps stopping" directly after starting it
I can't even send a rageshake
It happens after login and the first-sync-progress-bar
ftr 1.0.1-dev [205646062] (F-b3287) still syncs without issues after clearinf cache
The text was updated successfully, but these errors were encountered: