Hey, so I have a bunch of items that won’t install, saying they’re not compatible with my device. Thing is, they were all installed prior to my doing a reset. I just needed to get a fresh clean start after lots of testing stuff cluttered things.
OK so here are things to note: I’m using a Moto g stylus 5g 2023 (XT2315-1) genenv. Android 13. I have TWRP setup as my recovery, and I’m rooted with Magisk which is up to date.
I did not make any upgrades or downgrades of Android, I simple reset. Most things are working fine, but just some APKs won’t install.
It is possible that I had previously had an LSposed (Xposed variant) module installed which dealt with this; all it is, is an arbitrary minAPI designation but in no way actually has a compatibility problem. But try as I might, I don’t remember specifically installing a module to resolve this. Rather, I suspect perhaps it was dealt with inadvertently by something I happened to install. ¿maybe?
If anyone knows the solution to this, I’d be much-preesh.
Any time Play tells me I’ve an incompatible phone, I just use Aurora Store to install the app from the Play store.
I’m using neither, I am just installing with an APK file, as stated in my post.
Sounds like your play integrity is failing, which is, for some reason, checked by many apps who don’t really need it.
https://developer.android.com/google/play/integrity/overview
Open the Google Play Store app and tap your Profile Icon in the top right corner.
Go to Settings
About.
Tap the Play Store Version text 7 times in a row until you see the message “You are now a developer!”.
Go back to the General settings menu and tap on Developer Options. Tap Check Integrity to run the test.
Probably not if android is saying the apk is incompatible at install time, which I think is the case here.
Play integrity only takes effect once you actually launch the app (or install it from play I think)
I’m not installing from Play, I’m just using an apk file via package installer.
That doesn’t matter, play API services are built into the APK. That being said, as far as I know, the check actually happens when you launch the app, not when you’re installing it, so I’m probably wrong anyways
Not sure if it would help, but if you can try installing it with ADB instead, ADB gives much more helpful information on why it failed rather than a useless generic unsupported error message.
I’m gonna give it a try tomorrow actually. Will fup if anything develops. Thanks for the reminder. Hmmm maybe this would also be a good opportunity to setup and test ADB over network.
Good luck!
Based on your comments, maybe it’s because you have root and or unlocked bootloader. Android play store would not allow me to install animal crossing, it would give me the same error as you. Once I updated to a non root image, I was able to install the game. It’s also possible the app you are truing to install is 32-bit.
Not installing from Play store! Yes rooted, yes, unlocked bootloader and TWRP. And it was this way before, too, when it worked fine. I really don’t think Play store or services are involved at all. I even disabled them. No change.
I mean could be that you disabled it. And could new android version (even minor update). I never thought it would block me from installing an app on my pixel phone, but it did and I was only able to install the app once I removed root. Again, that worked before, but not this time.
No everything should be working it’s just not. Eventually I’m sure I’ll figure it out.
I will certainly give it a try, thank you! Actually I’m a bit under the weather and not thinking too clearly because I didn’t even think to try installing via ADB with I assume has command line arguments to skip the SDK level. Actually I do have an advanced installer app, which I haven’t yet thoroughly explored; maybe it, too, can handle this.
Also, the thing is, I have installed this on a dozen phones of differing Android versions and different phone models etc. with no problem. I think I have got it on some devices running Android 6 even.
I know that “this app isn’t compatible with your phone” error message is something I noticed often after upgrading to a phone that does not support 32-bit apps. Considering you seem to have not upgraded your phone or anything, that is unlikely the exact cause here. But I figured I would bring that up in case that thought of 32-bit incompatibility helps lead you in the right direction.
As I said everything is the same. I just reset using the Android reset. I tried using an advanced installer app and it claimed it was a Split apk - which it is not. That can happen if it doesn’t recognize the problem, it just throws up whatever is first in line.
Very weird shit. Its actually more than one app having this problem. I’ll figure it out eventually.
