Icon problems

Solar2D iOS
1

When I build my app on mac OS I get a warning 

WARNING: unrecognized key:  settings.iphone.xcassets (string)

and my icons don’t show up in the simulator nor on a real device.  

I copied the doc exactly so I can’t figure out why it doesn’t like my key. 

settings = { orientation = { default = "landscapeRight", supported = { "landscapeLeft", "landscapeRight", }, }, iphone = { xcassets = "Images.xcassets", plist = { UILaunchStoryboardName = "LaunchScreen", -- Required! UIStatusBarHidden = true, }, }, }

My directory structure looks like this:  

[sharedmedia=core:attachments:6973]

I am at a loss.   Any ideas? 

2

What version of Corona are you building with?

3

I downloaded what was on the front corona web page and ended up with 3135.   Is that the right one?  

4

You need to use a newer daily build.  I suggest the latest.

Rob

5

That is all it was.   I upgraded to 3175 and it works fine now.  Why isn’t a working build the default?   Another 2 hours wasted! 

6

Laura,

 I know this is resolved already, but  I suggest always using a daily build.

Realize that public builds can’t keep up (on a release schedule) with daily builds because they require a significant amount of work to test and publish.

if worst comes to worst and you find a bug in a daily build you can always roll back to a prior build OR wait for a fix in a future daily.  But, using public builds for releases is (IMHO) a bad idea because public builds always lag features.  

-Ed

7

Hi Laura.  Google and Apple are constantly changing things and we are constantly having to adapt. 

Rob

8

What version of Corona are you building with?

9

I downloaded what was on the front corona web page and ended up with 3135.   Is that the right one?  

10

You need to use a newer daily build.  I suggest the latest.

Rob

11

That is all it was.   I upgraded to 3175 and it works fine now.  Why isn’t a working build the default?   Another 2 hours wasted! 

12

Laura,

 I know this is resolved already, but  I suggest always using a daily build.

Realize that public builds can’t keep up (on a release schedule) with daily builds because they require a significant amount of work to test and publish.

if worst comes to worst and you find a bug in a daily build you can always roll back to a prior build OR wait for a fix in a future daily.  But, using public builds for releases is (IMHO) a bad idea because public builds always lag features.  

-Ed

13

Hi Laura.  Google and Apple are constantly changing things and we are constantly having to adapt. 

Rob