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.
After updating to Xamarin.iOS 188.8.131.52 and Xamarin Studio 5.10.2, any new images added via imagesets do not appear to be bundled correctly:
Could not load the "image" image referenced from a nib in the bundle with identifier "com.example.app"
Project and diagnostic build log are in the next comment - private due to production code.
In the project, Plus.imageset and LogArrows.imageset are two new imagesets that are exhibiting the issue.
This might be related to Bug 34762
This isn't related to bug #34762. That bug is due to a clash between the Library project and the main App project (you can't have Assets in both a Library project *and* the main App project - if you do, only the main App project's assets will be found at runtime).
In this case, the Assets are in the main App project and so that is not the issue.
This appears to be a bug in the caching logic for the CompileImageAssets task.
Reassigning to @kzu and his team.
I tested this on the latest Alpha (version info below) and the issue does not seem to occur. Modified the initial storyboard to include the images from the troublesome image sets and the images appeared at runtime with no errors.
Closing this as it appears to be working / fixed - please let us know if you are still affected by this.
=== Xamarin Studio ===
Version 6.0 (build 4520)
Installation UUID: 11a26d86-0d21-407a-8da9-8c197ecc0ad1
Mono 4.3.2 (mono-4.3.2-branch/ba2e5e4) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 403020467
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Apple Developer Tools ===
Xcode 7.2.1 (9548.1)
=== Xamarin.Mac ===
Version: 184.108.40.2064 (Business Edition)
=== Xamarin.iOS ===
Version: 220.127.116.114 (Business Edition)
Build date: 2016-02-24 16:50:28-0500
=== Xamarin.Android ===
Version: 18.104.22.1684 (Business Edition)
Android SDK: /Users/Adam/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.1
Java SDK: /usr
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
=== Xamarin Android Player ===
=== Build Information ===
Release ID: 600004520
Git revision: a354b2cb9df4b96f50b0ccb960dbdd5a9155510c
Build date: 2016-02-18 14:52:07-05
Xamarin addins: 8e54979f23feee160d245a3c33e43e77779b1eb4
Build lane: monodevelop-lion-master
=== Operating System ===
Mac OS X 10.11.3
Darwin Adams-Retina-MacBook-Pro.local 15.3.0 Darwin Kernel Version 15.3.0
Thu Dec 10 18:40:58 PST 2015