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

Element crashes in loop after initial sync #1709

Closed
lub opened this issue Jul 17, 2020 · 6 comments
Closed

Element crashes in loop after initial sync #1709

lub opened this issue Jul 17, 2020 · 6 comments

Comments

@lub
Copy link

lub commented Jul 17, 2020

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

@olmari
Copy link

olmari commented Jul 17, 2020

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..

@bmarty bmarty added this to the Post-Element release milestone Jul 17, 2020
@lub
Copy link
Author

lub commented Jul 17, 2020

I'm happy to gather logs via other ways, I just don't know how

@lub
Copy link
Author

lub commented Jul 17, 2020

I was able to send a rageshake :)

@kannanvm
Copy link

I had issues with v1 but updating to element-dbg 1.0.1 solved it.

@ganfra ganfra self-assigned this Jul 20, 2020
@ganfra
Copy link
Contributor

ganfra commented Jul 20, 2020

Should be fixed in next release, it's a proguard/realm issue. Thanks for pointing!

@ganfra ganfra changed the title f-droid release crashes after initial sync Element crashes in loop after initial sync Jul 20, 2020
@lub lub closed this as completed Jul 31, 2020
@bmarty
Copy link
Member

bmarty commented Aug 3, 2020

Fixed by #1766, thanks for the follow up @lub !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants