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.
If a referenced library project has bundle resources with the same name as bundle resources in the app project, the ones in the app project should take precedence.
This means we should unpack resources from libraries *before* copying the project's bundle resources.
fixed in git master
Fantastic! Any schedule for this to reach Beta channel?
I think that has the fix
Looks like this version doesn't extract XIB files from the library: images and text files (=content files) get over the resulting build, however, the XIBs from lib do not make it to the final app.
Actually, just noticed it does not extract Images sometimes as well (so far only during clean builds), so it looks like the bug is not actually fixed, but escalated :)
hmmm, this isn't going to be trivial to fix.
Going to revert & reopen for now.
n/m, found a way...
Well, the resources are now copied over in all scenarios (clean build, dirty build etc). However, the resources from libraries still take precedence over the ones in main project.
I verified this by placing 2 xibs named in the same way in a lib project and an app project. The builded app always has the XIB from lib project :(
Ah, I fixed it for everything but nibs
Fixed it for nibs now too.
Could you be so kind to compile one build with the fixes for me? :)
It's still uploading, so give it a minute.
Looks like it is actually working, thank you!
One more issue, however – seems that if a resource is touched in a library project, it would get over app's one (maybe some kind of dirty flag set leading it to be copied over?). Anyway, I appreciate this to be a different bug as the general flow is working just right :)
Thank you very much for you time and assistance!
Ah, right... because the list I'm adding to a "don't overwrite these"-hashset only included files that had changed since the last build... (which meant that it'd be empty for the main project) d'oh.
Okay, fixed that now, too.
Hopefully this build fixes the last of these corner cases.
Sorry for not providing feedback for couple of days. Yeah, looks like right now everything is in place (apart from few kinks which are rare and usually fixed by simple re-build). And as I do not see any obviously broken behavior, I would confirm the bug is fixed now :)
Thank you very much for your efforts, it helped our team a lot and saved many hours of development!
No prob, glad to be of service :-)
*** Bug 29016 has been marked as a duplicate of this bug. ***