Real world example. I’m updating our Lite version of Trisaic to reintroduce to the app store.
In Xcode but of course.
Choose distribution.
Select trisaiclite under the “targets”
Click on “Info” or the “i” button.
Select the properties button.
Identifier should read com.joroto.${PRODUCT_NAME}.
Change the version field to something meaningful. Increment it if you are publishing an update.
Choose the “Build” button.
Change “Configuration” to “Distribution”.
Go the “Code signing Identity”. Make sure it is set to “iPhone Distribution: Joroto, Inc.”
Close that window.
Choose Build and Build.
In Finder go to your project directory, into the build directory, go to “Distribution-iphoneos”.
Double click your ${APPNAME}.app in our case trisaiclite.app.
Choose Compress.
Run the AppLoader.
Choose the open slot for the upgrade.
Upload the application zip file.
If it fails, fear not, just be afraid. The dreaded “Codesign error” with absolutely NO explanation as to what it found wrong with your freaking zip file. Thanks Apple.
FIX IT YOURSELF I say. A CALL TO ARMS, and fingers.
We’re going to do it the old fashioned way. Screw the non-helpful graphical interface. Give me a terminal window.
Go to finder, applications, and run a terminal window.
cd to your project directory. Example of mine below (an underscore represents a SPACE not an underscore):
cd_/Projects/Trisaic/build/Distribution-iphoneos
You’ll see your app’s directory called in my case Trisaiclite.app. Yes this is actually a directory not a binary. The binary is buried in the directory. I like this construct.
Now you want to use the command line zip program like this. Again a real world example (an underscore represents a SPACE not an underscore):
zip_-y_-r_trisaiclite.app.zip_trisaiclite.app
OHHH Baby I feel the energy.
Upload this puppy to the app store AND IT WILL WORK!!! WOOHOO.
Everyone has this error and Apple still hasn’t figured out how to give us extended errors during the upload. Oh well, we like the rest of what they do.
