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.
Our project started out supporting iOS 7+, so we created all of the necessary launch images. We decided to remove support for iOS 7, and since 8+ can all use launch storyboards, we removed LaunchImage from the asset catalog, and all references to it from Info.plist and the iOS project file.
Even after doing Build-Clean, we continue to get the warning:
> 1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(985,3): warning : The launch image set "LaunchImage" has 5 unassigned children.
I have scoured our source tree (and all the intermediate dirs) for any reference to LaunchImage and it's all clean. The only thing I can think is that it got left behind on the OSX host and is still being referenced for some reason (I see several copies of LaunchImage.launchimage scattered throughout ~/Library/Caches/Xamarin/mtbs/builds/<myProject>)
If I check out the project on OSX and build with Xamarin Studio instead, the warning isn't there. It's only when I build from VS.
I can try reproducing with a new project if need be.
After making an ostensibly unrelated change (to the storyboard), the warning is no longer appearing. I assume whatever I did invalidated the badly-cached item.
I stand corrected. The warning is still appearing for the first build after a clean.
Hi Matthew, it would be great if you could provide a sample solution with some repro steps so we can try to reproduce the issue on our side. Thanks, Adrian
Apparently this issue has cleared up some time in the last few months. I am not seeing this on the current beta channel.
As per Comment 4 marking the bug as Resolved Fixed
As per comment 4 and comment 5 closing this issue.