Open theRoboxx opened 2 years ago
I'm having the same problem on a Samsung A71 running Android 12 and v3.1.5 of SafeDot. I didn't try accessing the log until after I enabled accessibility, but it kept crashing even after disabling it. I got the message mentioned by @kamaravichow and then after a few more crashes I got a different message saying it's crashing because of a bug in the app and suggesting I clear the cache, which I did to no effect. I also found that SafeDot worked even without enabling accessibility, so I'm not sure why/if that's actually needed.
Same
My issue seems to be the same as mentioned here: https://github.com/kamaravichow/safe-dot-android/issues/30
Description: First of all, the strange part is that the access log doesn't crash and shows the empty screen when the app is fresh installed and "Enable Safe Dot" isn't activated. I tested it again and it only crashes when i try to open the access log after I enable the accessibility setting. But if I deactivate the accessibility setting and try it again the app crashes differently and shows a "SafeDot keeps stopping"-window.
Additionally I should say that it worked on LineageOS 19-20220709-NIGHTLY-beryllium from two weeks ago. So it could also be a current Android problem.
I used adb on my laptop and the command
for the logs below. The errors seems to be identical but the codelines are different.
Just let me know, if you need any other information for debugging :v: .
package: com.aravi.dot version: 3.1.5 from F-Droid device: xiaomi pocophone f1 os-build: Android 12, LineageOS 19-20220723-NIGHTLY-beryllium