Geek Answers Handbook

Phased Deployment with Multiple APKs

I have the following situation. We have two in production APK:

  • Version 3.0.21 (API Level 7 +)
  • Version 2.14.2 (API Level 3 +)

I want to publish a phased deployment update for the 3.0 APK. So I:

  • Open dev console in advanced mode
  • Uploaded my new APK project to Production

Now I have three APKs:

  • 3.0.22 (API Level 7 +)
  • 3.0.21 (API Level 7 +)
  • 2.14.2 (API Level 3 +)

However, this configuration is incorrect. It says that "all devices that can receive version 30021 will receive version 30022." "Publish phased deployment button" is disabled.

To continue, I have to deactivate version 3.0.21, which leads to the following:

  • 3.0.22 (API Level 7 +)
  • 2.14.2 (API Level 3 +)

This seems wrong. What happens to current users 3.0.21 when I publish as a phased deployment? Will they end up in application 2.14 if they are not part of the phased deployment, or will AP.2 3.0.21 still be serviced?

It seems to me that 3.0.21 is not fully published. Perhaps I just misinterpreted the information. See below:

Screen shot of situation

+7
android google-play
source share
1 answer

I had the same situation as you and the same thoughts. However, I dared to continue posting the changes.

When I turn to crashes and ANR, I see that it still calls my existing versions (your 2.14.2 and 3.0.21) as "Current production" +, I have my new version (your 3.0.22) as Phased Deployment. Therefore, from this, everything seems good.

Google play developer console

I also just confirmed that people see the existing latest version (your 3.0.21) on the Play Store (and some people see that the version is deployed (your 3.0.22)).

Therefore, I find it safe to do multi-threaded deployment of an APK like this. :)

+1
source share

More articles:


All Articles