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.
Created attachment 5520 [details]
Solution that demonstrates the problem
Since build 1.8, the Xamarin.iOS plugin for Visual Studio fails to debug or deploy to an iOS device due to an exception:
System.InvalidOperationException: The operation cannot be completed because a build is already in progress.
at Microsoft.Build.Shared.ErrorUtilities.ThrowInvalidOperation(String resourceName, Object args)
at Microsoft.Build.Execution.BuildManager.BeginBuild(BuildParameters parameters)
at Microsoft.Build.Execution.BuildManager.Build(BuildParameters parameters, BuildRequestData requestData)
at Mono.IOS.VisualStudio.MonoTouchDeploySession.RemoteBuild(VSBuildServerClient server, Project project, IVsOutputWindowPane outputPane, MonoTouchProgressNotifier notifier)
Building locally works fine. It seems to fail as soon as the local machine decides to do a remote build. It doesn't even appear to contact the remote build server.
I am aware of the current bug where the Deploy checkbox on the Build Configuration dialog needs to be unchecked in order for deploying to work. I also tried the suggestion of limiting the parallel builds to one at a time. Neither of these workarounds solves the problem.
I believe I've found a significant clue to this bug. If I use the main menu in Visual Studio and select Build | Clean Solution, Build | Build Solution, and then Debug | Start Debugging, debugging on an iOS device works 10 out of 10 times. However, if I attempt to use the context menu on the project and select Debug | Start new instance, it fails about 25% of the time.
I have attached a simple solution that demonstrates the problem.
Here is my version information:
Microsoft Visual Studio Ultimate 2012
Version 11.0.61030.00 Update 4
Microsoft .NET Framework
Installed Version: Ultimate
Visual C# 2012 04940-004-0038003-02511
Microsoft Visual C# 2012
Windows Phone SDK 8.0 - ENU 04940-004-0038003-02511
Windows Phone SDK 8.0 - ENU
NuGet Package Manager 2.7.41101.299
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
Xamarin.Android 4.10.01073 (d23a19bf)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 1.8.365 (8cb9dbd0)
Visual Studio extension to enable development for Xamarin.iOS
This is a duplicate of an existing internal bug 16066. This has been fixes and should be in the next release.
Today we have checked this issue with following builds :
Xamarin for VS 220.127.116.11 (3f8cecdd5d00f0366e31218f111ce20c1c216cd0)
Xamarin.iOS 18.104.22.168 (Business Edition)Hash: 8400ec3
Now we are able to build and deploy attached sample on device and simulator successfully.
Hence closing this issue.