Closed bphd closed 1 month ago
@DerGoogler Why invalid and why not planned? It's almost like you don't want to work on your own project, why such behaviour? You could explain what it needs for it to be valid. Here it seems more like a method to avoid managing the issue altogether
The reason why I closed this issue is because that this issue has zero context (e. g. steps to reproduce). And those logs are the most useless in the app. Literally every native method could thrown that. But this error is most for Magisk user when they approve root for the app. Just re-launch in this case
@bphd
The reason why I closed this issue is because that this issue has zero context (e. g. steps to reproduce). And those logs are the most useless in the app. Literally every native method could thrown that. But this error is most for Magisk user when they approve root for the app. Just re-launch in this case
@bphd
So if that error is useless it means that the app doesn't log enough into Android logs, because that was all available on the logs, nothing more
Upon any re-launch that happens. It's a bad behaviour. The app should tell to grant permission and then should stuck at that request textually until granted, rather than literally crashing, explaining nothing of what it needs. Not every user use toast root request nor MagiSK. So bad behaviour
Java exception was raised during method invocation