We identified one or more issues with a recent delivery for your app, “…”. Please correct the following issues, then upload again.
Invalid Signature - A sealed resource is missing or invalid. The file at path [thunkablecompanion.app/thunkablecompanion] 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
You are right i am using own .certSigningRequest file. But how can i create Thunkable .certSigningRequest file because of i dont have Two Factor Authentication. When i watch this video it seems if i have Two Factor Authentication.
So how can i create Thunkable .certSigningRequest file without Two Factor Authentication?
*Certificates. If you have an existing Apple Developer Program account with 2 iOS certificates, you’ll have to revoke one. Apple only allows developers to have 2 iOS certificates at a time and Thunkable creates one when it publishes to your account.
I also uploaded one app 2 months ago and last month another app uploaded why now this happening?
Let me Explain my story about publish. 1. Turned off 2FA: I recieved this mail from Itunes Connect. After than i opened 2FA (You can see Second one)
We identified one or more issues with a recent delivery for your app, “…”. Please correct the following issues, then upload again.
Invalid Signature - A sealed resource is missing or invalid. The file at path [thunkablecompanion.app/thunkablecompanion] 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
2. Turned on 2FA:
I didnt login itunes connect from Thunkable.
I tried lots of time (another browser,another PC) for login (Ios Publish) it happen anything! Just processing again again again no error no login no second section seeing any different area or page.
Theese are really paradox.
When i close 2FA i will see 1.Option.When i open 2FA i will see 2.Option.
So what can i do?
(I did lots of procedure. Change my apple developer mail, password, clean cache or etc. nothing happen anything.I really mixed!)
I’m having the same problem.I followed the steps in the video on how to publish but got the same email from Apple Connect:
Dear Developer,
We identified one or more issues with a recent delivery for your app, “Cross The Bridge Project”. Please correct the following issues, then upload again.
Invalid Signature - A sealed resource is missing or invalid. The file at path [thunkablecompanion.app/thunkablecompanion] 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
Do you need to solve this error? Thunkable never answers me a way to solve this, just programmed answers. I’m running the risk of being sued, I need help with this.
So it’s been a week since I resubmitted and I haven’t heard back from Apple at all. i don’t even know if it has actually been submitted by Thunkable following the procedure on the video…
