element-hq / element-hq/element-android
Corrupted state and crash on resync
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- PR merge metrics
- No merged PRs in 30d
Description
### Steps to reproduce
I recently re-opened the app, and after a screen purporting to sync my data, I was greeted with a Space I frequent—but empty.
Tapping the Spaces button showed that Element thought I was in no spaces.
When pressing back, I was greeted by a list of rooms that were titled incorrectly, with no icons, and in no discernible order. Some of them were erroneously marked as empty.
When opening any of the rooms, all user profile pictures were missing. It was at this point that I noticed that my profile picture in the top left was missing, too.
After closing the app and re-opening it, I was shown a Space I had no recollection of with no rooms in it. After going back to the overview, I found that this “space” was in fact a room.
I went to the settings to check if my e-mail and username data was still there—it was.
After clearing the cache, Element crashed after a very long time of waiting for a server response, by showing a white screen and then ending with an ANR modal.
I reopened Element to see if the situation could be salvaged, and Element asked me to report the crash. I tried to, but Element crashed while reporting the crash.
After reopening Element again, I managed to successfully report the crash (hopefully).
Since I have background ANRs on, I received a number of crashes from Element even after closing it.
I have reported the original issue and the crash via the in-app reporting form as best I could, incl. logs etc..
### Outcome
#### What did you expect?
The app behaves normally.
#### What happened instead?
See steps above.
### Your phone model
Google Pixel 6
### Operating system version
GrapheneOS, based on Android 13
### Application version and app store
Element version 1.5.12, installed from Play Store
### Homeserver
matrix.org
### Will you send logs?
Yes
### Are you willing to provide a PR?
No
Contributor guide
Assessment
This issue has not been assessed yet.