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.
Default.png file isn't being copied into the output application directory any more, thus there is no more splash image.
To get around this, one has to manually create custom Post Build commands to just get it working on the Simulators, but Device builds are too complicated for this to be done easily.
This is a bug in MD 2.6 b3, you can work around it by using MD stable (2.4.x) or MD 2.6 b2. It's fixed in the upcoming 2.6 b4.
Does this bug affect ALL images in the root directory?
All Content files, yes.
The problem is not fixed in 2.6 R1
Several people are having similar issues with R1, see:
I agree. I tried with MD 2.6 RC1 and MT 126.96.36.199 and am still having the problem. By the way, I did not have the problem with MD 2.6 b3 and MT 4.0.3. I didn't see the problem until I upgraded MT to 188.8.131.52.
Now that you mention it, the problem came the day I installed 184.108.40.206 MonoTouch
I'm running MonoTouch 4.0.5 and still getting this problem. It's a complete showstopper for shipping an app, sadly :(
The bug is with the beta MonoDevelop release. If you use the stable (2.4.x) it works just fine and Michael posted that its fixed, but for the upcoming beta 4 release.
The bug is also in RC1.
A "Release Candidate" is not a beta; it's a candidate for a stable release. This release candidate has a show-stopping bug in it that prevents developers from shipping apps, therefore it should no longer be considered as a candidate for release.
I'm running MonoDevelop 2.6 RC1 with MonoTouch 4.0.5 (and 4.1, and 220.127.116.11) and this behaviour is the same as in MonoDevelop 2.6b3. I can build exactly the same codebase with MonoDevelop 2.6b2 and it works perfectly happily.
Has there been a code change between the shipping of RC1 and now to address this issue? Please don't mark this case as resolved unless you've verified the fix.
I can confirm on a MacBook Pro, MonoTouch 4.0.5, Mono 2.10.4 and MonoDevelop 2.6 RC1 that the same problem exists.
We're dead in the water.
*** This bug has been marked as a duplicate of bug 309 ***
Ok guys, I guess i found a workaround, please give this a try
Im running MD 2.6RC1, in order to your content files are being included in the
final bundle, delete them from your project, then save your project close MD,
then reopen MD and add again your content files to your project, don't forget
to mark them as content ;)
this worked for me.
Michael backported the fix, the next update will have it.
Assigning to Alex, so he can close it when 2.6 RC2 goes out.