Bug 4093 - iTunesArtwork file is not supposed to be set in Info.plist
Summary: iTunesArtwork file is not supposed to be set in Info.plist
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-03-26 09:03 UTC by Mikkel
Modified: 2012-10-15 15:55 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Mikkel 2012-03-26 09:03:14 UTC
When setting the iTunesArtwork file in Info.plist the file gets copied to the .app bundle - we're encouraged to do so by MonoDevelop's interface, but it's not supposed to according to http://developer.apple.com/library/ios/#qa/qa1686/_index.html. The file serves no purpose being in the .app bundle, increasing the total size unnecesarily.  

I suggest moving the iTunesArtwork file option to iPhone IPA Options under project's configuration.

Also, I would expect the file to named case-sensitive when copied to the IPA.
Comment 1 Jeffrey Stedfast 2012-03-27 14:30:44 UTC
I've fixed the capitalization to iTunesArtwork when copied into the IPA.

I'll look into the other issues momentarily.
Comment 2 Jeffrey Stedfast 2012-03-27 17:53:43 UTC
fixed in git master
Comment 3 Mikayla Hutchinson [MSFT] 2012-03-27 19:07:19 UTC
I don't think the artwork is an ipa-only option, because MD can also put it in the zip file for for uploading to the app store.

Unfortunately iTunesArtwork is not well documented by Apple.

What is clear:
* it should be called "iTunesArtwork", and should not have an extension
* it should be a png or jpeg (though some docs say png only)
* it should be 512x512 or 1024x1024 (retina)
* it should not be in the Info.plist
* in ipa packages, it should be in the root of the ipa

What's not clear:
* whether it should be in the app bundle. Apple's docs are ambiguous, third party web posts are contradictory.
* Apple's docs says you should have normal and retina images, but there is no information at all on how to include both in an app store or adhoc build.
Comment 4 Mikkel 2012-03-28 05:02:54 UTC
You're right, the documentation is very poor.

What about renaming iPhone IPA Options to iPhone Distribution (and have iTunesArtwork there) for now? You can add support for the unclear stuff when - hopefully - clarified.

While you're at it, why not rename the 'iPhone' part to 'iOS' for all project config sections?
Comment 5 Jeffrey Stedfast 2012-03-31 11:27:52 UTC
I don't think it's worth moving the iTunes image selector for now. There's a bunch of things in the "Plist Editor" that don't actually get saved in the Info.plist (e.g. launch images).

The uture plan is to be more like Xcode... have the convenient UI show up when the user selects the project itself, and not when they select the Info.plist. Instead, show the "Advanced" Plist editor when they select a plist.
Comment 6 Jeffrey Stedfast 2012-08-13 10:49:37 UTC
Now that Mountain Lion is out, Google is actually returning links with info about what the name of the 1024x1024 iTunesArtwork image should be named, which a number of developer blogs have stated is iTunesArtwork@2x (none have offered an alternative name, so it's probably accurate).
Comment 7 Jeffrey Stedfast 2012-10-15 15:55:44 UTC
this has been fixed