Gamesalad Uploader problem
MightyBoosh
Member Posts: 83
Can someone tell me if there is something wrong with the gs uploader. I can Publish my app ok but when I try to upload it to apple I get a code provisioning error. I know what this means as I have uploaded nearly 300 apps in my time but all the normal remedies are not working.
Any advice appreciated !
Cheers
Any advice appreciated !
Cheers
Comments
My adhoc builds have worked fine, but Im having no luck at all getting a working version that Application loader will recognise and allow me to upload.
Ive even completely cleaned out/removed all previous certificates and provisioning profiles, and generated new ones, to make sure im not getting any confusion... but its just not giving me an app that Application Loader will accept.
Im getting rather frustrated...as Ive been trying to get it done now for around the past 5-6 hours, and its now 6:30am...
Can anyone help...??.?.?
HELP!!!!
All you have to do is save the .App file on your desktop , then create new folder and drop the .app in that then compress it and in the app loader goto the folder and just choose the .zip file that you compressed
GOOD LUCK Hope It Works!
"####.app is not a valid location for the app. It must be at the top level of the archive"
any other ideas??
Started a fresh install of Gamesalad and Xcode (including downloading and installing all the provisioning profiles and certificates) on a different computer and it worked first go.
Looks like something on my computer is tainted... can i swear in this forum?? Just in case I cant "Fook".
At least we are up and running and I hope no one goes through the stress we did. Next thing to do is delete Xcode and Gamesalad and all provisioning profiles and certificates off my MBP and start again in the hopes that I can untaint my tainted MBP.
To make this (now longish) post very clear.
The problem was that we used Path Finder to compress the .app file. When we compresses the .app file directly in the Finder it worked perfectly and uploaded to ITC.
note: i assume any other compression method other than Finder could create the same problem. [edit: Path Finder uses the Stuffit engine for its compression]
Hope this helps no one else go through this. Quite a simple fix in the end. Thanks JohnPap for helping us head down what was the eventual solve.