Open lalalasupa0 opened 3 months ago
yokai_crash_logs.txt
Screenshot and crash log
Seems to caused by outdated database handler, can't be fixed until I modernized the database handler.
Probably fixed by https://github.com/null2264/yokai/commit/b17578365d292d6d32f4dba9968859539eba02ad, or at least partially... (You can test it on Nightly r5174 or newer)
yokai_crash_logs.txt Screenshot and crash log
This crash is definitely fixed, but I detected other similar crash.
@null2264 It started crashing in this r5373 update while reading
That's compose stuff, can't fix it, Google need to fix it unfortunately.
That's compose stuff, can't fix it, Google need to fix it unfortunately.
When you say Google has to fix it, it dashes my hopes You believe it could fix itself in future updates?
I also saw a lot of stuff regarding that compose thing in a google search, and this started happening with the new Yokai update only, maybe there is something in it idk
It's happening a loooooot, really, a looooooooooooot
Interesting, I'll try upgrading compose to newest snapshot and see if that helps, they did say they fixed it, but hasn't release it
That's compose stuff, can't fix it, Google need to fix it unfortunately.
When you say Google has to fix it, it dashes my hopes You believe it could fix itself in future updates?
I also saw a lot of stuff regarding that compose thing in a google search, and this started happening with the new Yokai update only, maybe there is something in it idk
It's happening a loooooot, really, a looooooooooooot
That has been resolved by Google on new beta release (https://github.com/null2264/yokai/commit/2471f454f8fd5e32014893cb9b8c38eb71060016)
REF: https://developer.android.com/jetpack/androidx/releases/compose-ui#1.7.0-beta04
Interesting, I'll try upgrading compose to newest snapshot and see if that helps, they did say they fixed it, but hasn't release it
It seems that it was fixed with that update (im not completely sure), I forgot to confirm it at the moment
Oh, nice.
Steps to reproduce
Delete or move an entry
Expected behavior
It does it, but...
Actual behavior
... The app is forcefully closed at the same time
Crash logs
The app doesn't give me one
Yōkai version
1.7.14
Android version
Android 12
Device
Samsung 10+
Other details
Might be an issue of my device, however, It is not a heating or battery optimization problem
Acknowledgements