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.
When I am connected to the MacBook I cannot build my iOS Application from Visual Studio 2017.
Android works fine however when I try to build iOS I get the following error message:
Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
Xamarin for Visual Studio v 220.127.116.115
Xamarin.iOS v 10.12.0.18
Xamarin.Mac v 18.104.22.168
This bug report does not contain a complete error message or log files. To make a reasonable guess, the issue might be a duplicate of Bug 58789 (and the follow-up Bug 58834).
## Next steps for the reporter
1. Update to today's Xamarin 15.3.2 Servicing Release https://releases.xamarin.com/stable-release-15-3-2/, and check if that resolves the issue. This release includes candidate fixes for Bug 58789 and Bug 58834.
2. If that does not resolve the issue, please collect and attach back your diagnostic build output:
a. Set "Tools > Options > Projects and Solutions > Build and Run > MSBuild project build output verbosity" to Diagnostic.
b. Also enable verbose mtouch output by adding -v -v -v -v under "Project Properties > iOS Build > General [tab] > Additional Options > Additional mtouch arguments".
c. The next time you build the project the diagnostic MSBuild output will now be visible in the Output window.
d. Once you hit the error again, you can save the diagnostic MSBuild output to a file via "File > Save Output As..." and zip it up.
e. Attach back the zipped output file.
Thanks in advance.
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!