0

I want to export my iOS app as an ipa file for Testflight. For some reason only on this project there is no option to build an .ipa file. Instead I can only export it as a Mac OS X application. It runs fine on the simulator and on the real device. I already tried recreating the Ad-Hoc Provisioning profile, but it didn't change anything.

Would be great if someone knows how to fix that.

Thanks in advance!

Xcode export dialog

enter image description here

2 Answers 2

1

I use TestFlight a lot and I do this:

Take the .app and put it in a folder called "Payload", compress that folder to a .zip file, then change the extension of the file from .zip to .ipa (you will have Payload.ipa), and your file is ready for TestFlight.

This is the way I do it and it works.

Sign up to request clarification or add additional context in comments.

5 Comments

You mean I should put the .app folder into a new folder called my project and zip it? Should I use the app folder from the simulator in the Library?
Yes, put the .app into a folder and zip it, and change the .zip to .ipa. But not the file from the simulator, change the scheme to iOS Device and press Command+B, and take that file, the other one is only for the simulator.
Okay, I can simply use the simulator app folder? I tried it and got this error: 'Invalid IPA: the .app must be in a "Payload" (case-sensitive) folder.' I'll try to create on and put it inside
Sorry I forgot to say that you have to call the folder "Payload.zip" and then "Payload.ipa". The .app from the Simulator is not going to work, change the Scheme to iOS Device and press Command+B to generate the .app for the device.
Okay, I built it and uploaded it to Testflight, but now I get the error "Invalid IPA: Must specify MinimumOSVersion" I'm not sure if that's really a good solution. There seems to be something wrong with the project settings. This is a property I shouldn't change on my own: stackoverflow.com/questions/846975/… I guess the organizer sets it automatically when exporting the app
1

I finally found a solution for this problem: I used the "Validate Settings"-button underneath the build settings. The only property Xcode changed for me was the deployment target from iOS 4 to iOS 5.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.