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 or GitHub 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.
Can we default new iOS projects to compiling against the Simulator instead of Device. A new developer machine may not have signing keys (mine does not) so by default when I try to compile a newly created project it fails.
The error is also not great as it just says "No signing keys found". It could additionally suggest "You may want to try compiling against a Simulator".
There is no explicit "default", it's all down to how MainToolbar.cs decides to load project configurations.
It just so happens that the first project configuration it loads is "Ad-Hoc" (alphabetical?) which cannot build for simulators, so it picks up the device as the default target.
This default target then gets set as the "ActiveExecutionTarget" and when it finally switches over to "Debug", it attempts to keep the ActiveExecutionTarget which happens to be the device target, and so selects that.
No clue how to "fix" this.
Reassigning to Lluis because he understands this code way better than I do.
This bug is not actual anymore because of the Xamarin Live Player feature.