I just built our app with the latest Fire (Xcode is 7.0.1), and when trying to upload it to the app store (for TestFlight) using application loader, but get this error:
ERROR ITMS-90529: "Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files."
Am I missing something?
Also, it would be nice for Fire to have an ‘archive’ function like Xcode, since I have to go and manually create the zip file for application loader to pick up.
It said so, but I’m creating it by compressing the .app
I’ve now seen that if I change the zip extension to ipa it goes a bit further but then I get another error (ERROR ITMS-90072: “The IPA is invalid. It does not include a Payload directory.”)
If you mean ‘Create ipa file’ under packaging (project settings for release), I did try that, but when I select it with application loader, it says “The package doesn’t contain an info.plist”
It’s been a while since I did this last time, and then all I did was compress the app then uploaded the zip file, but now it isn’t working.
That’s not bow it works. It needs a “payload” subfolder inside the zip
yep
weird. can you send me the project and/or .IPA? afaik it shouldn’t have an Info.plist inside the IPA (side from the one inside the .app of course). i assume your App does have an Info.plist?
I tried adding one. An empty one, and one with the app inside it, same error
The app certainly has one (I had to add some additional stuff after getting other errors about new things missing and it passes after making those changes, up to this point anyway) and I can see it if I view package contents of the app file. How do I look inside the ipa?
Something is odd then, since the one created is the same size as the app file, and compresses down a lot - I just renamed the IPA as zip and can’t uncompress it.
I’m assuming it didn’t make the build (not in release notes) as it’s still not working - it’s creating a huge file, but application loader still says “The package doesn’t contain an info.plist”
Sorry about that, looks like indeed this didn’t make it not the beta; it’s working fine here for me again, so i hope the next beta will fix this for you as well. Do you need an interim build?