Android

34224 readers

62 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

founded 3 years ago

MODERATORS

Rooki@lemmy.world

L3s@lemmy.world

L4s@lemmy.world

APK says app not installed because it isn't compatible with your phone. (lemmy.world)

submitted 1 month ago by AndrewZabar@lemmy.world to c/android@lemmy.world

20 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] REDACTED@infosec.pub 4 points 1 month ago (2 children)

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.

[–] Ghoelian@piefed.social 2 points 1 month ago

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)

[–] AndrewZabar@lemmy.world 1 points 1 month ago (1 children)

I’m not installing from Play, I’m just using an apk file via package installer.

[–] REDACTED@infosec.pub 1 points 1 month ago* (last edited 1 month ago)

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