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.
When trying to deploy an iOS app, it can fail because the SDKs are not "in sync". There is no indication that is why, just a generic VS dialog that says there were deployment errors and that it failed. Looking in the log files, there is an error message like this:
>[08-Sep-2014 12:28:16] Error: Invalid authorization data
>[08-Sep-2014 12:28:16] Error: Unauthorized request from <ip address here>
**Steps to Reproduce:**
1. Install an older version of the XVS plugin.
2. Instsller a newer version of Xamarin.iOS on the Mac build host.
3. Build and Deploy an app.
It fails with no indication of why.
An error message that might help indicate that they are not in sync, and specify which version of Xamarin.iOS needs to be on the Mac build host.
**Build Date & Platform:**
Updating the XVS plugin to the same channel as the build host resovled the issue.
With the replacement of Build Host with XMA, this kind of versioning issue has been fixed.
Now, the missmatch between iOS versions is informed to the user as a warning when the connection is made between Windows and Mac.
Also, if there is any error during build, deployment or launch process, it's also informed to the user via Output Pane, Error list or log file, according to the case.
Mark the bug as Fixed.