Closed sofiane-h closed 3 years ago
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.
When using this step, the deployed APK seems to deactivate by default the current available APKs. I would like to avoid this behavior because we have a mobile and a TV APK, and I would like to keep the TV APK when uploading the mobile one (vice versa). A simple solution would be to just disable this deactivation and retain by default all APKs already available in the Play Store, the Play Store would always use the highest versionCode anyway.
Is there a flag or something that I can use in the step for this?