Invalid Signature. Code object not signed at all... for iOS code submitted to Apple store.

[Richard DeVost]

First a note: The new stable 1.9 version and iOS toolchain to build the Xcode package are fabulous. The complete download and build were flawless--even numpy compiled without any hitches.

The build works great in the simulator and on devices I download the code to, but the submission to Apple is rejected because of ERROR ITMS-90035, Invalid signature. Code object is not signed at all... for binaries in the kivy and numpy paths.

The project was built using the command line as per the Kivy, Create a package for iOS documentation. In addition, I use my iPhone Developer identity/certificate in the Xcode Build Settings->Code Signing for both the project and the target.

Is another setting required to get the kivy and other libraries signed during the Xcode build?
Or, is there another way to build the kivy, numpy, etc. binaries to have them signed?

Thanks.

[Richard DeVost]

Still, no luck. I changed all identity and provisioning certificates to distribution instead of development and tried the following:

1. Clean then Build and Archive.
   
2. Added the following Run Script in Build Phases after Copy Bundle Resources: find "$CODESIGNING_FOLDER_PATH"/lib/python2.7/site-packages -iname '*.so.o' -exec codesign --force --sign "<my ios distribution certificate>" {} \;
3. Built an archive and ran a version of above command in the terminal to sign all the .so.o files in the archive before Submit to App Store....

The builds produce a working app that runs on an iPad and that successfully passes the Validate archive... with no errors. But it is not accepted by Apple because of an ERROR ITMS-90035, Invalid signature... for each of the .so.o files.

One clue may be that the first thing Submit to App Store... does is Preparing signing for assets for <myapp> and displays a list <myapp>.app followed by all the .so.o binaries. The <myapp>.app displays a Provisioning Profile of <my ios distribution certificate> but all the .so.o files have None as their Provisioning Profiles.

Has someone pushed up an iOS app to the store recently? What options or steps did you take?

Thanks.

[Babakutube]

Hi Richard,

Were you able to find a work around for this? I'm facing the exact same problem.

Cheers,

Babak

On Friday, May 22, 2015 at 12:11:14 AM UTC-7, Babakutube wrote:

[Richard DeVost]

Hi Babak,

Regrettably, no. Apple still rejects the upload even though it passes the validation step.
What do you think changed? Did Apple implement a stricter codesigning policy or is there a missing step in the new kivy-ios build?

I'll continue to experiment. Please let me know if you have a breakthrough. I'll do likewise.

Thanks,
Richard

[niavlys]

hi, it have been fixed:

https://github.com/kivy/kivy-ios/issues/133

update kivy-ios and rebuild kivy, or remove those so.o file by hand.

[Richard DeVost]

Hi niavlys,

Thanks for the reply. I got the app uploaded after installing the new toolchain AND deleting the so.o files.