Corona not recognizing xcassets when building

Solar2D iOS
#1

I have been trying to build using build 2017.3155, when doing so it errors out with the following error concerning the “Images.xcassets” folder:

Images.xcassets: error: None of the input catalogs contained a matching stickers icon set or app icon set named  “AppIcon”.
/* com.apple.actool.notices */
Images.xcassets: warning: Failed to read file attributes for “Images.xcassets”
    Failure Reason: No such file or directory

I’m getting this error even though I have the “Images.xcassets” folder in my project folder complete with the required icons. 

Anyone have any ideas what I need to do? Below is a screenshot of my project folder containing the Images.xcassets folder.

#2

Looks like you have other files within the Images.xcassets folder (e.g. intro.lua)

#3

Hey jeff15, It does look like it in the copy and paste of my files, but the other files are actually not in the Images.xcassets folder. So, it’s nothing to do with extra files.

#4

My suggestion would be to remove your icons and the folder and try dragging in one of the sample sets from the Corona sample apps to narrow the issue down further. Maybe post your build settings too?

#5

I was able to solve the problem by going back to the last public build 2017.3135 instead of using 2017.3155. Apparently, daily build 3155 can’t find the Image.xcassets folder in my project folder. But, once I went back to using 3135 I had no problems and the build was successful.

#6

I’ll see what we can find out.

Rob

#7

Just to be clear, iOS support for xcassets was added in 3143, so you are not compiling them when using 3135 and build.setting xcassets entry is just ignored.

#8

Hey vlads,

You are right. I didn’t think about when the support for xcassets was added. I went back and tried build 3144. Got the same errors as before. So I got to thinking…I wonder if it has something to do with the editor I’m using. I’m using Outlaw and calling the corona sdk from Outlaw. I tried it without calling corona via Outlaw and it worked.

So, obviously, the problem is with the editor calling corona. If I bypass the editor and go straight to corona I don’t get the error. I will contact Outlaw about the problem.

Thanks everyone for your help,

Guy

#9

I am having trouble with icons using the new the Images.xcassets procedure. I resolved by using the past procedure, including icons in root and build.settings. I am using latest xcode/macOS/corona, and building natively.  If there are known issues or other, I’d greatly appreciate guidance. I used the guide to implement, and tested a few different ways.

#10

Hello, [member=‘hfroth3’]!

Could you please provide some specifics of what exactly not working? Is there any errors? Did you try to build any of the sample from SampleCode folder, do they work?

#11

Hi vlads - 

Thanks for the quick reply. I’ll retry all, captured notes and repost that data. There are no error, but using the new procedure the icons are not showing/loading for the app (I see the missing icon, icon). 

#12

The issue related to associating the icons with the build for native builds. In ‘Target Membership’ I had to selected the checkbox next to my app build name/icon. This then associated the icons with my build. Thanks for the help.

#13

Looks like you have other files within the Images.xcassets folder (e.g. intro.lua)

#14

Hey jeff15, It does look like it in the copy and paste of my files, but the other files are actually not in the Images.xcassets folder. So, it’s nothing to do with extra files.

#15

My suggestion would be to remove your icons and the folder and try dragging in one of the sample sets from the Corona sample apps to narrow the issue down further. Maybe post your build settings too?

#16

I was able to solve the problem by going back to the last public build 2017.3135 instead of using 2017.3155. Apparently, daily build 3155 can’t find the Image.xcassets folder in my project folder. But, once I went back to using 3135 I had no problems and the build was successful.

#17

I’ll see what we can find out.

Rob

#18

Just to be clear, iOS support for xcassets was added in 3143, so you are not compiling them when using 3135 and build.setting xcassets entry is just ignored.

#19

Hey vlads,

You are right. I didn’t think about when the support for xcassets was added. I went back and tried build 3144. Got the same errors as before. So I got to thinking…I wonder if it has something to do with the editor I’m using. I’m using Outlaw and calling the corona sdk from Outlaw. I tried it without calling corona via Outlaw and it worked.

So, obviously, the problem is with the editor calling corona. If I bypass the editor and go straight to corona I don’t get the error. I will contact Outlaw about the problem.

Thanks everyone for your help,

Guy

#20

I am having trouble with icons using the new the Images.xcassets procedure. I resolved by using the past procedure, including icons in root and build.settings. I am using latest xcode/macOS/corona, and building natively.  If there are known issues or other, I’d greatly appreciate guidance. I used the guide to implement, and tested a few different ways.