Xcode Creates Wrong IPA Folder Structure

Xcode creates wrong IPA folder structure

Make sure the key "LSRequiresIPhoneOS" in the info.plist has the value "YES", and make sure the key has the correct case, i.e., IPhone versus Iphone. Earlier versions of Xcode were not as picky about that.

Xcode 4 & three20 & create IPA archive: No such file or directory

The Three20 documentation did not solve this issue for me (unfortunately...). Eventually what worked for me was a mix of a few solutions. There is a difference between "Archive" and "Build for Archiving" (or build for run) and using these steps I have both of them working with no build issues:

You will need to change the scripts as Manni mentioned, set the "Skip Install" flag for each Three20 project linked to your project tree and add the following paths to your project's "Header search paths":

"$(BUILT_PRODUCTS_DIR)/../three20"
"$(BUILT_PRODUCTS_DIR)/../../three20"

this will get you to work with the Build option. When you want to perform the archive action, then you will also need to change the "Locations" preference in Xcode as featherless mentioned above.

I documented these steps in this post.

How to convert .xcarchive to .ipa for client to submit app to app store using Application Loader

I also observed the same problem in one of my projects.

I resolved it by changing settings in target. For main project and dependency.

 skip Install  NO

After this change, goto Xcode->Product->Archive->Save for Enterprise or Ad-Hoc Deployment

We followed the same process and uploaded through Application Loader and Apple approved the app.

Invalid IPA: the .app must be in a Payload (case-sensitive) folder.'

Make sure the key "LSRequiresIPhoneOS" in the info.plist has the value "YES"

Invalid Swift Support / The SwiftSupport folder is empty

important note: this only works for projects that do not use swift, see comment below

I just met the same issue and resolved it by making the following change -
If you used to have Swift files in your project but then removed them, you only need to set "Embedded Content Contains Swift Code" to NO in Build Options.

---

Related Topics