Binary rejected

[davemikesell]

I just uploaded a new version of Diver Down, using the same Corona and Xcode that I used for the last release a couple weeks ago.   

Got this.   Not sure why, though they did reject the large app icon before submission because it had an alpha channel (PNG).  I changed that to JPG.   Do all icons have to be JPG now?

What a meaningless error message.   Apple’s app store submission process is patently awful.   I can’t believe a company that makes such great products is so woefully incompetent in so many other areas.

We have discovered one or more issues with your recent submission for “Diver Down”. To process your submission, the following issues must be corrected:

This bundle is invalid  - The file was not a valid zip file.

[ingemar]

I’ve never seen the PNG error before, but I’ve always created my PNG files without alpha channel.

I use Photoshop to create my app icons + large icon (1024x1024) and use “Save for Web…”, and make sure Transparency is not selected.

I haven’t uploaded a new app/update in the past month but maybe Apple is changing things… again.

The invalid bundle is weird though. Are you using the latest Corona daily / Xcode 6.1? If not, maybe Apple is preparing to enforce usage of their latest build-tools, but haven’t got the error messages in place yet. It may be an issue with the upload as well. Maybe it got corrupted during upload.

[davemikesell]

I’m using Xcode 6.1 and the latest Corona release (2393a).    I’ll try with all icons with no alpha channel.    

I’m using a script that exports from inkscape, and don’t see a way to export sans alpha, so I added ImageMagick’s convert to the tool chain to remove the alpha channel.

[ingemar]

2393a builds with the iOS 7 SDK if I’m not mistaken.

I’m not sure, but maybe Apple is starting to be a bit restrictive and want new builds to be built with the iOS 8 SDK.

Also, I don’t remember Apple being picky about alpha before. Maybe yet another restriction with their new portal.

[davemikesell]

I get a warning that I’ll have to start building for 64-bit soon, but it accepts the binary.

Still “Waiting for Review” a half hour later…yesterday they rejected in 13 minutes.   Fingers crossed.

[ingemar]

The 64-bit warning is fine. CoronaLabs will be adding 64-bit support later but it will take some time.

They’ve said that it will be ready before it becomes a requirement…

Maybe the “invalid binary” was a temporary glitch in the previous upload. Fingers crossed.

[ingemar]

I’ve never seen the PNG error before, but I’ve always created my PNG files without alpha channel.

I use Photoshop to create my app icons + large icon (1024x1024) and use “Save for Web…”, and make sure Transparency is not selected.

I haven’t uploaded a new app/update in the past month but maybe Apple is changing things… again.

The invalid bundle is weird though. Are you using the latest Corona daily / Xcode 6.1? If not, maybe Apple is preparing to enforce usage of their latest build-tools, but haven’t got the error messages in place yet. It may be an issue with the upload as well. Maybe it got corrupted during upload.

[davemikesell]

I’m using Xcode 6.1 and the latest Corona release (2393a).    I’ll try with all icons with no alpha channel.    

I’m using a script that exports from inkscape, and don’t see a way to export sans alpha, so I added ImageMagick’s convert to the tool chain to remove the alpha channel.

[ingemar]

2393a builds with the iOS 7 SDK if I’m not mistaken.

I’m not sure, but maybe Apple is starting to be a bit restrictive and want new builds to be built with the iOS 8 SDK.

Also, I don’t remember Apple being picky about alpha before. Maybe yet another restriction with their new portal.

[davemikesell]

I get a warning that I’ll have to start building for 64-bit soon, but it accepts the binary.

Still “Waiting for Review” a half hour later…yesterday they rejected in 13 minutes.   Fingers crossed.

[ingemar]

The 64-bit warning is fine. CoronaLabs will be adding 64-bit support later but it will take some time.

They’ve said that it will be ready before it becomes a requirement…

Maybe the “invalid binary” was a temporary glitch in the previous upload. Fingers crossed.