bitrise-steplib / steps-google-play-deploy

MIT License
54 stars 38 forks source link

Deploy to multiple flavors to different apps on Play Store #56

Closed richardansell closed 3 years ago

richardansell commented 5 years ago

How would it be possible to use $BITRISE_APK_PATH_LIST envvar to deploy each APK flavor to different apps on the Play Store rather than a single app?

bitce commented 5 years ago

Hi @richardansell, can you please send us a build URL where this is happening to you? The path list should contain all APKs.

richardansell commented 5 years ago

Hi @richardansell, can you please send us a build URL where this is happening to you? The path list should contain all APKs.

Hi @bitce, the problem is actually to do with the deployment of each APK flavor to different apps on the Play Store as I understand the path list contains all of the apps/flavors. It seems the Google Play Store Deploy step only allows the deployment of a single app to the store, rather than cycle through each flavor and deploy to different apps

bitce commented 5 years ago

@richardansell I understand, can you please still include a logfile or an URL we could check out about this?

github-actions[bot] commented 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.

github-actions[bot] commented 3 years ago

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.