Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We removed the Ad-Hoc and AppStore configurations from new projects on VSMac a long time ago.
I think the intention there was to simplify the number of configurations people have to maintain and avoid "dead configurations" (people make funny changes, don't touch it for a while, release with it and everything break).
We could discuss that internally if you want #ios but I think it'd be great to align both IDEs on this.
How does a user build the IPA from a CI environment if we remove Ad-Hoc and AppStore configurations?
We don't have a functional iOS Archive Manager yet, but even if we did, there's still the CI scenario unaddressed.
Is there anything we're missing here?
We use the release | iPhone configuration to generate the IPA.
Users can enable the IPA generation in their Release (or even Debug) build configuration and it'll generate the IPA.
This was never tied to an Ad-Hoc or AppStore configuration - those were just convenient build configuration names that we could auto-configure some stuff for users with likely values.
Thanks for the clarification.
Moving to CONFIRMED. We'll remove those configurations from the templates.
Fixed in version 18.104.22.1680 (master)
Commit: 9b4a93cdd0bdbf897e6771a8ab32531969dff1b7 (xamarin/XamarinVS)