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.
The current File -> New Project -> iOS menu does not have the unified project templates nested under Unified API like Xamarin Studio does. This causes confusion and mistakes when creating a new projects. Users are choosing the Unified API templates by mistake because they are more obvious to select then expanding Classic API first.
Unified templates should be nested in a Unified API menu option (similar to how Classic API templates are nested) similar to Xamarin Studio so the choice is more obvious.
Our goal is to have users use unified api. Starting next year Apple will only accept packages that include a 64bit version. So as stated before, this is by design.
This is correct, but the setting should only be done when the iOS Unified API stabilizes, and right now it is not stable. We are not freezing that API until next week.
I didn't know that. This is the way it's been since iOS8 shipped (and Unified was included). Does it make sense to change it now?
Checked, currently Unified API menu option (similar to Classic API templates are nested) doesn't exist.
Xamarin 220.127.116.11 (10cfd178d55287f09c85f5a1e604dfe20889a40f)
As discussed with Miguel via Hipchat, this is not an issue and will not be fixed.