-
Notifications
You must be signed in to change notification settings - Fork 9
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
Crash when reading old cache #22
Comments
Oh this one is my bad actually because |
Wait... No that isn't it, that class was scrapped |
Ahhhh that is it, and I made a mistake scrapping it. Essentially, the 5.1.4 |
So yeah I'll fix that later today |
Ah. Bigger issue. Because of how JVM serialization works, you can't rename a class and still deserialize things properly, so I need to see what I can do, but it may be that 4.x.x caches will not work with 5.x.x and I'll need to start designing a more long-term-stable cache format. |
Technically solved, and the new cache format is WIP now. |
Unfortunately this bug seems to keep reappearing😄 The clean install of 5.1.4 works perfectly fine (also thanks for crediting me in the release notes) but when updating from 4.0.1 with an existing save file it crashes again.
However this time its reproducible in the Emulator, so maybe that helps in getting rid of the bug.
Steps to reproduce:
I appended the full crash log at the end, but the only relevant lines are
I don't really get why it crashes, because there is try catch blocks everywhere that should have caught that exception.
Mabye its worth considering to use a different way of storage, since these FileOutPutStreams etc. are a bit tricky to debug. Since the data is very simple, you could use Android's Shared Preferences, and save the list as a serialized string in a single key value pair there. Or if you want to debug the current system, here is the full crash log:
The text was updated successfully, but these errors were encountered: