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.
I build from Visual Studio 2015 (up to date) with the latests up-to-date xamarin plugins.
I have an iOs app deploying fine on my device.
I created a todays' extension and referenced it from my main project.
It deploys nicely on the simulator but when I try to deploy it on my device, I get this error :
Tool exited with code: 1. Output: ditto: can't get real path for source '../../TVST.iOS.TodayExtension/bbab0075a4479dbc3ffaa583c620852f/bin/iPhone/Debug/device-builds/iphone8.1-10.3.3/TVST.iOS.TodayExtension.appex' TVST.iOS.UI C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets 1518
I noticed that, on disk, there is no "/device-builds/iphone8.1-10.3.3" folder with files in it.
Thanks for your help.
Created attachment 24678 [details]
Visual Studio build logs
IIRC this might be an issue we had if the "device specific build" option was not the same for both the extension and main project (which should be fixed in an upcoming release).
Can you check the project options of both the main and extension projects, and see if this is the case (and if so, change them to match; you can either disable or enable both, that's your choice).
Thanks a lot Rolf, you saved my day !
(This was indeed the issue)
*** This bug has been marked as a duplicate of bug 56748 ***