Missing info.plist value

Solar2D General Questions/Discussion
#1

When I try to upload my app to the App Store, I get an email saying “A value for the info.plist key ‘CFBundleIconName’ is missing” 

I followed these instructions

https://docs.coronalabs.com/guide/distribution/xcAssets/index.html 

My icons are located in my app’s root directory > Images.xcassets > AppIcon.appiconset 

and are all named and sized as required. 

My build settings file:

iphone = { xcassets = "Images.xcassets", plist = { NSAppTransportSecurity = { NSAllowsArbitraryLoads=true }, UILaunchStoryboardName = "LaunchScreen", CFBundleIconFiles = { "Images.xcassets/AppIcon.appiconset/Icon-40.png", "Images.xcassets/AppIcon.appiconset/Icon-58.png", "Images.xcassets/AppIcon.appiconset/Icon-76.png", "Images.xcassets/AppIcon.appiconset/Icon-80.png", "Images.xcassets/AppIcon.appiconset/Icon-87.png", "Images.xcassets/AppIcon.appiconset/Icon-120.png", "Images.xcassets/AppIcon.appiconset/Icon-152.png", "Images.xcassets/AppIcon.appiconset/Icon-167.png", "Images.xcassets/AppIcon.appiconset/Icon-180.png", "Images.xcassets/AppIcon.appiconset/Icon-1024.png"}, }, },

I tried removing the CFBundleIconFiles table but that didn’t fix it. 

#2

Go to the Corona welcome window and create a new project. Copy the build.settings and Images.xcassets folder from there (make sure to get the entire folder and it’s contents and subfolders).

This should work.

Rob

#3

I tried that. I tried everything. I still keep getting this email.

Dear Developer,

We identified one or more issues with a recent delivery for your app, “”. Please correct the following issues, then upload again.

Missing Info.plist value  - A value for the Info.plist key ‘CFBundleIconName’ is missing in the bundle ‘’. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7.

Best regards,

The App Store Team

#4

What version of Corona are you using?

What version of Xcode do you have installed?

Rob

#5

Xcode version: 10.1
Corona version: 2018.3326 (2018.6.25)

#6

I recommend getting the latest daily build and trying that.

Rob

#7

I just tried that, it didn’t work.
Am I supposed to have an info.plist file in my app folder? Or is there something wrong with my build.settings?

#8

I solved the problem! It was all because of the contents.json file. I used a website to generate the icons for me, and all I did was rename the files. I completely ignored the contents.json file. I just thought of opening it and all the file names were in a different format. I copied the contents.json file from a new project and that fixed it. Thanks!

#9

I’m glad you solved it. I created a new app from Corona 3470 and uploaded the build to Apple and it processed it correctly.

Somehow the contents.json file seems to get missed a lot, which I don’t understand where that comes from since doing a File->New Project, or downloading the zip file from GitHub or any other source where we give you working apps, that file ends up not being in the final source.

To help me track down why this is a problem for quite a few people, how did you get your Images.xcassets folder in your project in the first place? Where did you get the original files? Maybe the documentation isn’t clear.

Rob

#10

I used the makeappicon.com website to generate my icons. This site already creates the AppIcon.appiconset folder for you. So I replaced my entire folder with the folder made with this website, and then renamed the file names. I didn’t think of checking the contents.json file which still had the incorrect file names in it.

#11

Go to the Corona welcome window and create a new project. Copy the build.settings and Images.xcassets folder from there (make sure to get the entire folder and it’s contents and subfolders).

This should work.

Rob

#12

I tried that. I tried everything. I still keep getting this email.

Dear Developer,

We identified one or more issues with a recent delivery for your app, “”. Please correct the following issues, then upload again.

Missing Info.plist value  - A value for the Info.plist key ‘CFBundleIconName’ is missing in the bundle ‘’. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7.

Best regards,

The App Store Team

#13

What version of Corona are you using?

What version of Xcode do you have installed?

Rob

#14

Xcode version: 10.1
Corona version: 2018.3326 (2018.6.25)

#15

I recommend getting the latest daily build and trying that.

Rob

#16

I just tried that, it didn’t work.
Am I supposed to have an info.plist file in my app folder? Or is there something wrong with my build.settings?

#17

I solved the problem! It was all because of the contents.json file. I used a website to generate the icons for me, and all I did was rename the files. I completely ignored the contents.json file. I just thought of opening it and all the file names were in a different format. I copied the contents.json file from a new project and that fixed it. Thanks!

#18

I’m glad you solved it. I created a new app from Corona 3470 and uploaded the build to Apple and it processed it correctly.

Somehow the contents.json file seems to get missed a lot, which I don’t understand where that comes from since doing a File->New Project, or downloading the zip file from GitHub or any other source where we give you working apps, that file ends up not being in the final source.

To help me track down why this is a problem for quite a few people, how did you get your Images.xcassets folder in your project in the first place? Where did you get the original files? Maybe the documentation isn’t clear.

Rob

#19

I used the makeappicon.com website to generate my icons. This site already creates the AppIcon.appiconset folder for you. So I replaced my entire folder with the folder made with this website, and then renamed the file names. I didn’t think of checking the contents.json file which still had the incorrect file names in it.