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.
We're getting lots of "Cannot copy <file> as the source file doesn't" errors when trying to build from VS to Xamarin Build Host. Build in XS works, but cannot deploy from VS (actually, it takes several builds to deploy from VS, very annoying).
Error logs and VS info are attached.
We're seeing that this similar bug has been marked as resolved: https://bugzilla.xamarin.com/show_bug.cgi?id=26606
Is migrating to Unified API the only solution?
Created attachment 9892 [details]
Source file doesnt exist errors
Created attachment 9893 [details]
Visual Studio and Xamarin.iOS version
The version information from comment 2 shows XamarinVS version 3.9.289 (39a70ae), which _has the bug_ (as noted in bug 26606, comment 0), so I'm going to mark this bug as a duplicate of bug 26606.
XamarinVS 3.9.344 includes the fix for bug 26606, so version 3.9.344 will stop the problem in many cases. But as a caution, note that there is still one particular scenario where this error will still occur in 3.9.344: when the assembly name for the class library does not match the project name. I have filed a new bug for that second problem here: Bug 27665.
If neither bug 26606 nor bug 27665 matches the problem in your particular case, feel free to reply on this bug report (bug 27166), or feel free to send us an email via email@example.com to let us know.
Xamarin Customer Support
*** This bug has been marked as a duplicate of bug 26606 ***