Invalid Signature on itunesconnect.

[usmanmughal.uog]

Hi Guys,

Suddenly Corona build is not accepted on itunesconnect. It was accepted fine 4 days ago with same Corona build and same Application Loader. I tried on various Corona builds including latest one.

Dear Developer,

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

Invalid Signature  - A sealed resource is missing or invalid. The file at path [appname.app/appname] is not properly signed. 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

Best regards,

The App Store Team

Here is my plugins, may it’s a issue of any plugin.

plugins = { ["plugin.facebook.v4a"] = { publisherId = "com.coronalabs" }, ["plugin.OneSignal"] = { publisherId = "com.onesignal", }, -- key is the name passed to Lua's 'require()' ["CoronaProvider.analytics.flurry"] = { -- required publisherId = "com.coronalabs", }, ["plugin.google.play.services"] = { publisherId = "com.coronalabs" }, ["plugin.google.iap.v3"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true } }, ["plugin.amazon.iap"] = { publisherId = "com.amazon", supportedPlatforms = { ["android-kindle"]=true }, }, ["plugin.kidoz"] = { publisherId = "com.coronalabs" }, ["plugin.reviewPopUp"] = { publisherId = "tech.scotth", }, ["plugin.firebaseAnalytics"] = { publisherId = "tech.scotth", }, ["plugin.fabric"] = { publisherId = "tech.scotth", }, ["plugin.facebookAnalytics"] = { publisherId = "tech.scotth", supportedPlatforms = { iphone=true, android=true, ["android-kindle"]=true } }, ["plugin.zip"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true, osx=true, win32=true } }, ["plugin.firebaseConfig"] = { publisherId = "tech.scotth", }, --["plugin.flurry.analytics"] = --{ --publisherId = "com.coronalabs" --}, ["plugin.tenjin"] = { publisherId = "com.coronalabs" }, },

I tried a project in Xcode with same certificate and same provisioning profile and submitted through Application loader to ituneconnect. It accepted.

What is this problem and it’s solution. Thanks in advance.

Regards,
Usman Mughal

[rob]

What changes have you made in the past four days?

Rob

[usmanmughal.uog]

I added two composer scenes after that. But nothing changed in build.settings nor config.lua since that.

[rob]

I’ve seen this happen if you try to output your build into your project folder and the next build tries to include the previous build. You might want to make sure your output folder is not your project folder.

Rob

[usmanmughal.uog]

I’m sure I’m not using same folder nor next build tried to include the previous build. I tried the same code that I submitted IPA by attaching head in git repo. Still same error.

[usmanmughal.uog]

My thoughts are any plugin started to create problems. Can you check which plugin is updated recently?

I would try to remove plugins one by one to test but it will take time. I only can check it by making IPA and submit to itunesconnect and wait for Apple to approve or reject it. Development and Adhoc IPAs are working fine.

[usmanmughal.uog]

It’s very funny bug of Apple. Problem is somehow APFS filesystem or updating to macOS High Sierra.

I was fighting with this issue since 3days, uploaded a lot IPAs to Testflight during this period with different tests but nothing helped. The solution is, I placed source code onto 16gb usb formatted with HFS+ filesystem. And output path is also usb drive. I uploaded IPA from usb to itunesconnect and it accepted. Here is the reference. https://forums.developer.apple.com/thread/89187

Thanks Rob for kind support. Apple should fix this ASAP. It’s affecting native developer as well, may be native ratio would be less than cross platform.

Usman Mughal

[rob]

Apple is wanting to move everyone to APFS anyway, so it’s weird they are running into this.

I’m glad you found the source of the problem.

Rob

[rob]

What changes have you made in the past four days?

Rob

[usmanmughal.uog]

I added two composer scenes after that. But nothing changed in build.settings nor config.lua since that.

[rob]

I’ve seen this happen if you try to output your build into your project folder and the next build tries to include the previous build. You might want to make sure your output folder is not your project folder.

Rob

[usmanmughal.uog]

I’m sure I’m not using same folder nor next build tried to include the previous build. I tried the same code that I submitted IPA by attaching head in git repo. Still same error.

[usmanmughal.uog]

My thoughts are any plugin started to create problems. Can you check which plugin is updated recently?

I would try to remove plugins one by one to test but it will take time. I only can check it by making IPA and submit to itunesconnect and wait for Apple to approve or reject it. Development and Adhoc IPAs are working fine.

[usmanmughal.uog]

It’s very funny bug of Apple. Problem is somehow APFS filesystem or updating to macOS High Sierra.

I was fighting with this issue since 3days, uploaded a lot IPAs to Testflight during this period with different tests but nothing helped. The solution is, I placed source code onto 16gb usb formatted with HFS+ filesystem. And output path is also usb drive. I uploaded IPA from usb to itunesconnect and it accepted. Here is the reference. https://forums.developer.apple.com/thread/89187

Thanks Rob for kind support. Apple should fix this ASAP. It’s affecting native developer as well, may be native ratio would be less than cross platform.

Usman Mughal

[rob]

Apple is wanting to move everyone to APFS anyway, so it’s weird they are running into this.

I’m glad you found the source of the problem.

Rob