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.
After updating to Xamarin 3.1 Trial users are unable to deploy iOS apps from Visual Studio
The build succeeds but deployment errors out with the following log:
1>Server returned an error. The remote server returned an error: (500) Internal Server Error.
1>Server error code: 500
1>Internal Server Error
1>TrialCheckChanges failure during build
1>Exception thrown: Object reference not set to an instance of an object
1>Remote build step failed.
I have checked this issue and able to reproduce this. To reproduce this issue I have followed the steps mentioned below :
1. Open VS 2013 and login with any xamarin trial/business account.
2. Open Xamarin.iOS Build Host and login with any xamarin trial account.
3. Create a simple iOS application using VS 2013.
4. Try to deploy this app on simulator or device and got the error.
Note : If we have logged in Xamarin.iOS Build Host with any xamarin business/enterprise account instead of trial then we are not getting this issue.
Screencast : http://www.screencast.com/t/XFpBh2mfMh1H
Build Log : https://gist.github.com/ShrutiSaini360/dfa657edce585a35393c
Mac Server Log : https://gist.github.com/ShrutiSaini360/d2191f7199add7b7f1c1
Environment Info :
Xamarin.iOS Build Host 126.96.36.199
Duplicate bug #20613
This should be fixed in C6