Google Play console: does deactivation of production code version in alpha or beta tracks also deactivate the production apk?

Question

I have a weird bug in Google Play console that makes impossible to roll-out my apk from internal test track to closed track (beta). I have got the error message \'Fully Shad

Answer 1

Solved the problem.

What I did is :

1) upload the apk directly in production version

2) bug 'apk shadowed'

3) come back to previous page and click 'deactivate' in order to change the current production apk from 'retained apk' section to 'apk to be deactivated' section (not the exact names but you will see)

4) the bug disappears and you can submit. I don't know if a 'deactivate' of the production version in a alpha or beta version would deactivate the production version on the store ; I did not test ! :)

At the moment, I don't know if this 'bug' is the new behaviour of the Google Play console (that requires to deactivate manually the previous apk when a new apk is submitted) or a bug.