Corona creating extra 'icon' file during iOS build

Hi everyone,

When building for iOS distribution, I noticed an extra file in the .ipa. I discovered this after receiving an error in Application Loader saying an icon file name contained invalid characters. Turns out just to be a empty file that’s called ‘icon’ with no extension. See image attached.

Found another forum post that describes the same issue: https://forums.coronalabs.com/topic/43349-error-messages-after-trying-to-upload-to-apple/

Unlike that guy, I was not able to successfully submit after removing empty icon file and zipping. The invalid icon error does resolve, but it creates another problem of the certificate signing. Could unzipping and rezipping the ipa bundle cause this error? The signing error did not occur until I removed the empty icon.

Here is the full error after removing the empty icon file: 

ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

Please help!

Once you tamper with a signed IPA it becomes invalid.

I don’t see a stray ‘icon’ file generated when building with 2017.3081.

Are you using the latest public build 2017.3068 or later?

Version 2017.3081 (2017.5.17)

this is what I am using for building  

Are you sure you don’t have a stray ‘Icon’ file in your Corona project directory?

Also, I assume the name of your app isn’t Icon?

You are correct on both accounts.

Should I try building on an older version of corona?

The strange thing is that I don’t see an extra ‘Icon’ file in the resulting iOS app bundle after building with 3081.

Have you seen this in any of your other projects ?

Are you building on a networked drive or a cloud drive like Google Drive or Dropbox?

Are  you outputting your build to a networked drive or a cloud drive?

Can you run the Terminal (/Applications/Terminal.app)  and change directories to your project and do an “ls -ltr” command and copy/paste the results here?

Thanks

Rob

That was it! I am using Dropbox to store all my project files. This also meant that I was building directly from that dropbox folder. I think dropbox adds their own hidden/non-hidden files that caused the issue I experienced.

I copied all files to another folder stored only on my local HDD, and built/re-uploaded the app. Everything works!

Thanks again for your help @Rob @ingemar_cl

Once you tamper with a signed IPA it becomes invalid.

I don’t see a stray ‘icon’ file generated when building with 2017.3081.

Are you using the latest public build 2017.3068 or later?

Version 2017.3081 (2017.5.17)

this is what I am using for building  

Are you sure you don’t have a stray ‘Icon’ file in your Corona project directory?

Also, I assume the name of your app isn’t Icon?

You are correct on both accounts.

Should I try building on an older version of corona?

The strange thing is that I don’t see an extra ‘Icon’ file in the resulting iOS app bundle after building with 3081.

Have you seen this in any of your other projects ?

Are you building on a networked drive or a cloud drive like Google Drive or Dropbox?

Are  you outputting your build to a networked drive or a cloud drive?

Can you run the Terminal (/Applications/Terminal.app)  and change directories to your project and do an “ls -ltr” command and copy/paste the results here?

Thanks

Rob

That was it! I am using Dropbox to store all my project files. This also meant that I was building directly from that dropbox folder. I think dropbox adds their own hidden/non-hidden files that caused the issue I experienced.

I copied all files to another folder stored only on my local HDD, and built/re-uploaded the app. Everything works!

Thanks again for your help @Rob @ingemar_cl