A warning and a solution for exporting iOS IPAs using Cordova
A warning and a solution for exporting iOS IPAs using Cordova
- Subject: A warning and a solution for exporting iOS IPAs using Cordova
- From: Alex Zavatone <email@hidden>
- Date: Fri, 10 Feb 2017 09:33:54 -0600
OK. This is a great one that happened and was solved earlier this week. Took 14 hours to solve (4:30 AM) and because of an unfriendly error message in Xcode. Both in Xcode 8.7 and 7.x.
One of our team members implemented a solution in Cordova and we merged this into our iOS app and we have been using this for some time, at least 6 months.
Come time to export a flavor of our app and upload it to iTunes Connect, the app that we have been building, using, exporting as ad hoc for a year, while uploading it, the process reported that it wasn't code signed.
Error: ITMS-90035: "Invalid Signature. Code object is not signed at all. …
A paragraph of text followed. But the actual file that was triggering this error was never reported.
Viewing the activity and log in the Application Loader while uploading the IPA, at a quick glance, I could see at least 9, maybe up to 15 individual reports of this error.
Nowhere was the actual file that caused this error mentioned. > : [
I made sure the code signing was properly applied and accurate and and it was. Finally, I decided to pull the entire section of our app that was reliant on Cordova out of our app and we were able to upload the app to ITC without the error.
The issue apparent'y lay within the files in our build process that were included when adding Cordova.
Surprisingly, in our Copy Files phase of Build Phases, there were a bunch of .bat, .sh and other files within the Cordova folder that had no extensions on them.
The files within the Cordova folder that had no extensions? They were binaries, Unix executables. Our team member had just dragged the entire the bulk of his files into our Copy Files phase of our build process. These CLEARLY were executables and CLEARLY were not signed with any code signature.
: /
I removed them, Cordova worked, so did our build and we were able to upload our app to ITC.
Sweet mother of can I get one night's sleep per week?
But it took 14 straight hours on this problem alone and yet another overnight work session to figure this out. Of course, if the error messages were A LITTLE MORE DESCRIPTIVE, and listed the name of the file that actually caused the problem, this could have been solved in 15 minutes, I'm hoping that my tip will save some of you this sleep deprivation experiment if you proceed to use Cordova in your project.
The tip here is that when getting the "Error: ITMS-90035:…" error message when uploading an iOS app to ITC, PLEASE CHECK THE FILES IN YOUR BUILD PROCESS. Since this time, the error message was correct but the actual files that caused the problem were not indicated, it's likely that someone who is not you added files to your build that cause this error.
I hope that my painful sleep deprivation experiment will save some of you from going through the same experience.
I'd say, "cheers," but after one 48 hour continuous stretch, one 26 hour stretch and another 23 hour stretch in the past week dealing with Xcode export and delivery issues in the past week and a half, well, I'll just say good luck, instead.
Good luck,
Alex Zavatone
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden