Bug 11581 - Validate for iPad app archive fails with "Missing 57x57 icon" in XS
Summary: Validate for iPad app archive fails with "Missing 57x57 icon" in XS
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0.1
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
: 22345 ()
Depends on:
Blocks:
 
Reported: 2013-04-04 08:32 UTC by Allie Miller
Modified: 2015-11-17 16:16 UTC (History)
5 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Allie Miller 2013-04-04 08:32:13 UTC
After I updated to V1.1 in Xamarin studio, I validated the project in Xamarin studio and system shown me error "no 57 * 57" icon, but QuickPlan (the application name) is just for iPad. There is no problem when I validated it using Xcode.
Comment 2 Jeffrey Stedfast 2013-04-08 12:51:08 UTC
We get the requirements from Apple's web server (it's a set of validation rules in JSON) and so if we are checking for a 57x57 pixel icon, then Apple is telling us to check for a 57x57 icon.

Maybe Xcode doesn't use those validation rules that Apple's servers send?

Will have to investigate...
Comment 3 Jeffrey Stedfast 2014-08-25 17:57:13 UTC
*** Bug 22345 has been marked as a duplicate of this bug. ***
Comment 4 Phil Morris 2015-02-15 15:47:43 UTC
Same issue for me (iTunes reported missing 57 x 57 icon, yet it was in the resources folder when doing a build, and indicated in the .ipa file (built with VS2013).  After a number of failed attempts to fix this problem, I  decided to simply open the ipa file with 7zip, manually dragged all the required icon files onto the open zip to add them (even though entries were there), saved the zip, and was able to upload the ipa file with no errors.

BTW there should be far better documentation regarding the addition of icons using VS2013.  After a few hours of frustration where my icons (under source control of course) could not be added, I came across a comment regarding readonly files.  Images that are readonly cannot be added to info.plist via the properties window.  VS2013 simply reports that an error occurred adding the icon file.  Not very helpful, made worse by the error indicating the file name was icon.png, yet I was attempting to add an image by another name (57x567.png).  Only later did I realise that no matter what I had named the image file, VS2013 (Xamarin) was renaming the file to what iOS wanted (which is good).  Some additional documentation regarding this process would have saved me a couple of hours!
Comment 5 John Miller [MSFT] 2015-03-18 15:19:33 UTC
I had another case where this happened. The xcasset looked fine, and so did all the json and .plist files. Originally the app was targeting iOS 4.3 and up. Changing it to 5.0 stopped the error. 

Perhaps something is not working when targeting iOS 4.3?
Comment 7 Jeffrey Stedfast 2015-04-24 16:53:46 UTC
iOS 5 introduced a new CFBundleIcons key in the Info.plist. Before iOS 5, you had to use the CFBundleIconFiles key instead. Apple's Asset Catalog compiler generates values for CFBundleIcons but not CFBundleIconFiles.

That said,

1. John's customer in comment #5 did not have problems with the Validation script (which is what this bug report is about), he had problems submitting to the App Store.

2. Phil Morris's problem has to do with Visual Studio and not Xamarin Studio and sounds like he had the same issue as John's customer from comment #5, but is not related to this bug report at all.
Comment 8 Jeffrey Stedfast 2015-11-17 16:16:12 UTC
closing since none of the duplicates are actually this problem