-
Notifications
You must be signed in to change notification settings - Fork 25
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
TransactionTooLargeException when navigate from apps list to individual app crashes list #45
Comments
May I ask how many crashes you had collected to cause this, just for curiosity's sake? |
Over 200. Can't say now as I've cleared the history after creating this issue. |
Oh geez lol. Yeah perhaps you should've cleaned that up beforehand. Regardless, I'll need to figure out if I can handle the exception gracefully so the app doesn't straight up crash. |
This is not a right way to fix this. I'm an Android developer myself. I see the app is currently saving the whole crashes list in onSaveInstanceState. This "state" has a limit of 512KB in size. It's not really meant to store unbounded lists. A more correct way would be to use a ViewModel. It would download all crashes when the VM is being initialized. The crashes list would be stored in a variable in VM. Then when the user returns back to MainActivity, it would just observe data from VM. Then you don't need onSaveInstanceState. I see the app code is quite old. Feel free to ask any questions, I'm happy to help. Maybe I'll be able to contribute something to this app in the future, but I don't have much free time at the moment. |
@insiderser Honestly I agree. The app needs to be pretty much fully rewritten to use modern architecture (MVVM, AndroidX Room, etc.). I'm doing pretty much doing the best I can to keep the app functioning well enough for the foreseeable future until I am capable of rewriting the app completely and actually have the time to do so. |
Steps to reproduce
Expected behavior
Can see the list of crashes of the selected app.
Actual behavior
Crash:
Reproduction Rate
100%
Workaround
Clear the crashes history.
The text was updated successfully, but these errors were encountered: