CFBundleIconName?

Question

Created Sep ’17

Replies 9

Boosts 0

Views 21k

Participants 8

Hi all,

I'm trying to release a new version of our app. Archiving and uploading seem to go well. The build appears in ITunes Connect under Activity as 'processing'. After about 10 minutes the listing disappears and I get this e-mail:

Dear developer,

We have discovered one or more issues with your recent delivery for "<project>". To process your delivery, the following issues must be corrected:

Missing Info.plist value - A value for the Info.plist key CFBundleIconName is missing in the bundle '<project_id>'. Apps that provide icons in the asset catalog must also provide this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

The link just gives some generic info about asset bundles. We indeed didn't have a CFBundleIconName key set, but there's no docs on what it's supposed to be. Setting it to our project name or an image file name doesn't change anything - same e-mail as above.

I doubt if it's relevant, but here's what our info.plist says regarding icons:

<key>CFBundleIconFiles</key>

<array>

.... 11 more ....

</array>

<key>UIPrerenderedIcon</key>

<true/>

Any hints please? This prevents us from releasing a work-around for an iOS 11 problem.

Thanks,

Frank

Boost

Answer 1

KMT OP

Sep ’17

See Listing 1 and it's associated discussion, here:

https://developer.apple.com/library/content/qa/qa1686/_index.html

0

Answer 2

Starkode OP

Sep ’17

I am having the same problem here, this is something new that we have to figure out. I couldn't find anything related to 'CFBundleIconName'. In addition, XCode and Simulator is very slow on my brand new 2017 MacBook Pro 15". I start running iOS 11 to check all my apps and looks like iOS 11 has plenty of bugs.

Link that provided KMT is super old, it doesn't have to do anything with this new bug.

The latest way to do it since iOS 10 was setting the plist file as you describe it.

<key>CFBundleIconFiles</key>

<array>

<string>Icon-Small</string>

...

</array>

I am going to start troubleshoot today and see what happen.

0

Answer 3

KMT OP

Sep ’17

>super old

Last updated: 2016-12-20 for Xcode 8 - approx. 6 months after iOS 10 was released.

>this new bug.

I'm starting to wonder if it's just an issue on the backend, and not to do w/the tools/iOS.

Be sure to file, and don't forget to add your report # to this thread for reference, thanks and good luck.

Ken

0

Answer 4

eracube OP

Sep ’17

Hi there,

From Xcode 9 onwards we need to provide App Store icon sized 1024x1024 within the Xcode itself. This can be done by adding Image Assets from Asset Catalog [ ➕ -> App Icons & Launch Images -> New iOS App Icon ] and fill out all the required Icon image sizes.

The CFBundleIconName in Info.pList will be the same as App Icon name that you have provided. (Default value is: AppIcon)

If you were not using assets catalog, now it is the time to migrate to it.

Thanks.

0

Answer 5

bubble OP

Sep ’17

"If you were not using assets catalog, now it is the time to migrate to it."

But I can't find anywhere that says using assets catalog is required for this version.

0

Answer 6

Starkode OP

Sep ’17

Exactly, now assets catalog "seems" to be required. I moved to assets catalog and it passed. It may be a temporary backend messsage error until they evaluate properly, but for the moment it worked with assets catalog.

0

Answer 7

Martin.Krischik OP

Sep ’17

Damm. Great when you find out on release day that you have to migrate to something you did not even knew it exists. And you don't know how it works.

I like to migrate on my own terms, when I have time and patience to do so.

I am also not a graphic designer. I don't touch or want to touch the images.

0

Answer 8

krzyzanowskim OP

Oct ’17

Does the rule include app extensions? The Xcode 9.1b2 warn if app extension icon set does not have AppStore icon in it.

0

Answer 9

JeremyJFA OP

Apr ’18

I have encountered a similar problem when I changed deployment target to 11.3 and then changed back to 9.3. Now I can upload the app using the 11.3 target but not with the 9.3 target!

I have tried everything - the plist is correct etc but nothing works for 9.3 which leaves me with a problem for older phones and iPods

Jeremy

0