4
votes

My iPhone app icon shows up fine in iPhone/Retina and iPad. But on iPad retina (simulator and device) I get an icon that apparently contains the app's start screen:

enter image description here

Given that my app is designed for iPhone only (not 'Universal'), there is no option in Xcode 4.3 to add an iPad retina icon.

How can I get my app's icon to display correctly on iPad Retina devices?

2
I'll be the one to ask...why do you want your icon to display on iPad if the app doesn't run on iPad? - Ian Henry
App runs on iPad in the same way that all iPhone apps run on iPad. The window is as large as an iPhone. You get a "2x" icon in the lower-right. Clicking it enlarges the app. AFAIK, this is nothing unusual. The real problem is the icon. - Rich Apodaca
@IanHenry: ADG says so (see 2.10). The simulator has all kinds of problems related to icons and bundle resource refreshing BTW. So long as this works on a regular device, it'll be fine. - CodaFi

2 Answers

7
votes

In Xcode the target summary interface where you add your icons and launch images is merely a graphical interface to the Info.plist file. When you make a iPhone only target, the graphical interface for the iPad portion is hidden. To add information to the Info.plist file that isn't covered by the graphical interface move to the Info tab and enter it there. To add the Retina iPad icons add an icon named [email protected] and [email protected] to the Icon files array in the Info section. Also add actual 144 x 144 and 100 x 100 png representations of your icon with the proper name to your Xcode project and the target.

0
votes

I've just had this problem with an app too, and when I went to edit the Info.plist file found that [email protected] was in the icon list - no idea how it got there, but this project has been going on a while so could be a result of one too many XCode upgrades.

Removing it from the entries in the plist has fixed the problem on the retina iPad too. Am still going to add the extra iPad icons in just in case, but if others are having the problem it is worth checking what XCode has put in those entries.