Closed johanw666 closed 10 months ago
Interesting. I don't know what's going on here... The update to JRPN 15 was rejected by the play store, too. Maybe for the same reason? In my code, I don't do anything with ad IDs, or anything like that. This might be related.
OK, it looks like the advertising ID thing is a red herring. That's deep in Google's code. I note that it says "Update ad debug logging enablement as false", which is fine by me, since I'm not doing ads of any kind.
The reason this APK isn't working is because the Flutter android project I was using for that build was badly obsolete. I switched to using a Github workflow for the debug APK I was publishing on github, and the setup was a little different, in a way that made me use obsolete Android code that the Flutter dev environment had auto-generated.
I think the fix for this for now is for me to just remove the debug APKs from github. Once I get the play store issue resolved, do you need a debug APK from github for anything? I might just stop publishing them, since it adds a step for little benefit, and it causes confusion.
That probably explains why I could not compile it myself, getting an error about mismatching Kotlin versions in libraries.
JRPN 16C or 15C? jrpn 15 2.1.10
Describe the bug When I install jrpn 2.1.10 it crashes at startup.
Debug Log System log shows these errors:
Why does it even want to read an advertising ID? Due to the apk being signed with a debug key?
Platform: Android 11, play store not available and advertising service in Google Play services disabled.