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

All I did was update the version and the bundle code. My version had been set at .13 and I changed it to 15. My Bundle was set to 13 and I changed it to 15. It let me post it fine after I did that. I am in open testing.

Answer 2

I had exactly the same issue and resolved it by using the following versionCode entry in config.xml:

<widget id="io.cordova.hellocordova"
  version="3.1.1"
  android-versionCode="3001001"

Here android-versionCode is critical. It must be an integer greater than the number associated with last APK that you have uploaded. Due to some reason my previous version had an additional zero in between creating a higher number which went unnoticed. Since I can't change that because its published I added a zero in the new versionCode and made it 3001001 instead of 300101.

Worked perfectly.

Hope that helps.

Answer 3

Update :- Talked to a Googler working with Google Play console team regarding this issue. One misconception I had at the time was that you need to retain an APK if you want to have a staged rollout. I discussed this with him, and he clarified that it is not needed. Even in staged rollout, with no retained APK, Google play will show an install option to users who visit the app's page. Hope this clears doubts for someone facing similar issues.

I was having the same problem and I fixed without clicking "Retain" for previous version and uploaded a new one and then "Start Rolling" button turn into clickable and done!! ^_^

Answer 4

For me it worked the following way:

• First send a rollout only with the version you want to deactivate.
• Secondly, send a rollout with the version you want to publish to Beta.

Seems that under certain conditions Google Play cannot handle deactivating and publishing at the same time.

Answer 5

That's the solution of this problem. just disactivate the older version of the apk then you will be able to rollout the new version.

Answer 6

We ran into this problem as well with split APKs. We assigned version code for each ABI with the following gradle (simplified):

ext.abiCodes = ['universal': 0, 'arm64-v8a': 1, 'armeabi-v7a': 2, 'x86': 3, 'x86_64': 4, ...]

android {

  applicationVariants.all { variant ->

    variant.outputs.each { output ->
      def abiName = output.getFilter(OutputFile.ABI)
      def abiVersionCode = project.ext.abiCodes.get(abiName)

      output.versionCodeOverride = variant.versionCode * 100 + abiVersionCode
      ... 

With that we will have these APKs:

| ABI       | Version Code |
|-----------|--------------|
| universal | v100         |
| arm64-v8a | v101         |
| arm64-v7a | v102         |
| ...       | ...          |

And we got this "Fully Shadowed APK" error on APK v101. The reason is that any device that is on arm64-v8a will be able to install v102 since it is backward compatible.

Problem solved after we make the version code of armeabi-v8a higher than arm64-v7a.

ext.abiCodes = ['universal': 0, 'arm64-v7a': 1, 'armeabi-v8a': 2, 'x86': 3, 'x86_64': 4, ...]

You should watch out for this too.