Google Play - Fully Shadowed apk

Question

I have an existing app on the PlayStore. I am releasing new version of the app as staged rollout. However, I am not able to publish the app due to \"Fully S

Answer 1

Easy way to handle this problem is something similar like,

Seems bugs on play store

Answer 2

Note: this solution works for the time it was posted if doesn't work in the future don't consider it wrong because things changes with time.

You have to deactivate previous version while uploading a new APK that works for me. Simply deactivate previous versions and upload a new APK and roll it out for production.

Answer 3

in your release manager you see your last uploaded apk and on your apk you see the word retain click on it scroll down page then you see Deactivate option then click on it then upload your new apk again the n save to draft and review it then roll out and after that just wait .

Answer 4

You must build in this way to solve the problem

First: armeabi-v7a
Second: x86
Third: arm64-v8a
fourth: x86_64

Like this:

3000467 - armeabi-v7a
3000468 - x86
3000469 - arm64-v8a
3000470 - x86_64

Answer 5

Got the same problem here, issue most probably brought by the new release manager.

It feels like that the previous release (the one already in prod) is somehow stuck in alpha, preventing the new one to be rolled out.

Google support contacted and waiting for resolution (I'm working for an app with +25millions downloads, this issue is really something serious, hope google will take care of it really quickly)

In the meantime, we never used the beta channel, so we solved our problem by using it.

Answer 6

Problem:

This APK will not be served to any users because it is completely shadowed by one or more APKs with higher version codes.

Resolution:

Remove this APK from your release or review the targeting and version codes of the APKs that you are including in this release.

I got the same error when I tried to update my app. The Project was old and was in Eclipse, I fixed it by decreasing targetsdkversion from 27 to 26, because imported, supported android lib was Android 7.1.1, I don't know how it worked, but it works for me. :D