Closed abelyeupear closed 2 years ago
Hello @abelyeupear, do you have a pull request connected to this issue? 🙂
Nope. The previous step we used was deprecated so we were forced to move to this new one and it doesn't have the same functionality as the old one. If this were to allow AppCenter to set distribution groups, and not force to do it via this step, it would be 1:1 the deprecated step.
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.
Still an issue.
@abelyeupear you might be interested in the latest release where a new input was added to target all distribution groups.
That will do! Thank you.
Issue description
Reopening https://github.com/bitrise-steplib/steps-appcenter-deploy-ios/issues/4 because AppCenter's dashboard already has a way to add the appropriate distribution groups, so with this issue we are transferring that responsibility to the Bitrise step, which shouldn't be the case.
Ideally, not setting the
distribution_group
prop just let's AppCenter decide that for you. Today, not setting this prop doesn't distribute the app to anybody.