Start a new topic

iOS Distribution to AppStores fails - Invalid Signature

Hi Wikitude-Team, 


we added the new WikitudeSDK 7.1 to our App with the cordova-plugin (v7.1.0-3.5.2). But we have problems to upload the App to the AppStore. 


We get the following two distribution errors:

  

iTunes Store Operation Failed
ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [SCIO AR.app/Frameworks/WikitudeSDK.framework/strip_wikitude_framework.sh] 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" 

   

iTunes Store Operation Failed
ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [SCIO AR.app/Frameworks/WikitudeSDK.framework/wikitude_bitcode.sh] 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"


The building of the App on our testing devices ran without problems, we just had to put the WikitudeSDK to the Embed Frameworks Build Phase. 


In the AppStore Upload Wizard we get a the info that for WikitudeSDK.framework no profie is required. And its also not possible to set one. 



Best regards,

Philipp



2 people have this problem

Hi


I'm Also facing same issue.


image


Hi


Yes we follow the same still issue are there.

image

Hi, are you using the JS or Native API SDK? Because that makes a difference in the shell command (Framework name is different).


Best regards,
Andreas Schacherbauer

Hello support team,

We also got the same problem about Wikitude SDK while uploading app to AppStore.
We are using 7.1.0 SDK as it was purchased with license key.

You are saying that this issue is resolved in Wikitude SDK 7.2.0 but if we used that SDK we are getting license key missing issue.

Will we have to purchase it again?

Please find the attched upload issue image for reference (Using Wikitude 7.1.0 SDK)

Please suggest solution as fast as possible. Thanks in advance.


image

Tried adding suggested shell scripts. But still getting the same issue.

We are using Wikitude Javascript iOS SDK 7.1.0

Hi,

The scripts should work just fine ;) You could also use the ones from the 8.1 download package. The documentation also contains sections on how to use those scripts from outside the .framework bundle.


Best regards,
Andreas Schacherbauer

Hello,

I am currently working on an application (Xamarin iOS) and I am having this same problem. How can I solve it ?, since evidently the IDE that I use is Visual Studio and NO Xcode.

I appreciate that you provide me with an adequate guide to solve this problem, , since the one that appears in the link: (http://www.wikitude.com/external/doc/documentation/latest/ios/ios-framework-scripts-architect. html? _ga = 2.193255979.703125108.1541435295-1673602308.1524687650 # ios-app-store-submissions) is not oriented to Visual Studio.


Additionally, the version of the Wikitude SDK that I am using is:

Xamarin.Wikitude.SDK.JS 8.1.0


This is the error message I get from Application loader:


ERROR ITMS-90035: "Invalid Signature, Code object is not signed in. The file at path [XX.iOS.app/Frameworks/WikitudeSDK.framework/strip_wikitude_framework.sh] is not properly signed. 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 to Simulator target, if you are certain your code are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html "

ERROR ITMS-90035: "Invalid Signature, Code object is not signed in. The file at path [XX.iOS.app/Frameworks/WikitudeSDK.framework/wikitude_bitcode.sh] is not properly signed. 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 to Simulator target, if you are certain your code are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html "

Hi Wilbert,

For Xamarin we changed the NuGet package a bit as our scripts have no chance to remove those files as they are bundled into the .dll. We're about to release the update in the next few days but if you want to give it a try upfront, you can download a pre-release version here


Please make sure that the NuGet package is replaced (we know from other customers that it might still catch the old one, so please do a full clean build).


Best regards,
Andreas Schacherbauer

Login or Signup to post a comment