Building an archive in Xcode does not create an archive

Question

It seems that all my searches to understand this are fruitless. Knowing me, this is one dumb checkbox or drop-down list, I miss. Maybe this is my setup? Do I need to uninstall Xcode 4 and reinstall?

I went through all these steps, tricks and corrections all over the network and on SO, but nothing brings me closer to having the archive appear in my organizer. When I go to look at the archive that was built, it is just a file with zero k. I get a successful build, change skip install to yes and no ... I do everything that I find on the network, I'm crazy. I am almost sure that all my certificates are configured correctly, I have things checked where they tell me to be checked. It drives me crazy. 99% of the solutions I see:

“In any case, in“ Skip installation ”set“ Release ”to“ NO ”(the reference document told you otherwise). Once you set“ NO ”, back up again. You will immediately see your application. Appears in the organizer's archive" .

Well, that doesn't work, or any further answers after that either.

Answer 1

Archive seems to include those builds that are installed “installed,” so make sure you turn off Skip Install in the build settings:

• Go to the BuildSettings section.
• Find "Skip Installation."
• Select "NO" to release.

In addition, Xcode requires Install Path . For applications, this is usually /Applications , but when, for example, creating a plug-in, you can only install it on / , which places the build product in the root of your archive. Note that you should use the "real" path, not the relative one, for example ~/Library .

Answer 2

Make sure you use Product> Archive and not Product> Build For> Archive.

Answer 3

I had this problem after I upgraded to High Sierra. I went to my library folder. / Users / your_user / Library / Developer / Xcode / Archives This folder had an empty folder with the name of the date when I created this archive. But the folder was empty. I deleted the folder and archived again. This fixed the problem for me.

Answer 4

For me, I also had to change the following setting of an empty assembly, to something like ...

 "Installation Directory" --> /Applications 

Finally, he appeared in Organizer / Archives.

PS Interestingly, without this setting, an old archive file was created, but it was always empty.

Answer 5

I had this problem and for me it resolved the following:

• Code Verification. Signing on release is configured for your distribution profile. I did this, and it actually brought him back at some point. Make sure the setting has not been canceled and try again.
• You mentioned the value “Skip Installation", I also had similar results. Installing in YES will not open the list of archives by setting the value to NO.

Hope this helps (moreover, that helps # 1).

Answer 6

Go through this checklist and you should find the answer somewhere:

• Create a new schematic labeled "[Application Name] -AppStore"
• Create an assembly configuration labeled Distribution by duplicating the release
  • Click on the project and click on the configuration + under the assembly on the "Information" tab.
• Define the archive for the assembly as "Distribution" according to the new scheme.
• Check all certificates
• Check all training profiles
• Confirm your secret key under your name in the keychain. (in system keychains)
• Make sure that when you sign the distribution code, you install the profile in your iPhone / iPad distribution profile in all instances of the signature.
• Make sure your iPhone / iPad distribution profile is included in your project information for signing the distribution code.
• Make sure you have the option, skip the installation, in the build settings of your target set the value is "NO" for distribution.
• Make sure your currently selected scheme is "[Application Name] -AppStore> iOS Device"
• If nothing else, clear all assemblies, delete all attempts of the old archive, create for archiving, and if there are no other errors, try archiving again. One of the problems I ran into was when I let Xcode always allow a subscription with my private key. Just deleting this and reloading the certificates, Xcode again asked me to allow code signing. I am only now resolving, and I have not had this problem yet.

If you still have problems, you must delete all your settings, cancel all your certificates, reissue them all, and reinstall them all. Try resetting the code after this, and if it still doesn't work, use one of the two free TSIs provided by Apple Dev Support. If nothing works, they can fix it for you. I'm sure.

Hope this helps.

Answer 7

I did the following to make it work for me:

• I replaced some subprojects / static libraries that I had (i.e. three20) using cocoapods to include files in the main project .. he just got rid of all the problems that three20 gave me (and there are many ..)
• install skip installation to yes in accordance with the build settings for all other subprojects / static libraries and switch the copy headers from the public to the project in the assembly phases
• : in sub-libraries. In the build phases, I ensured that the destination for copying files was changed from the Absolute path to the products directory .

and all!

hint: to get an idea of ​​files with a violation that cause your archive to create an archive file, not ipa:

• Select the archive and click the "Distribute" button.
• Select the "Save embedded products" option.
• Click Next and Save.
• Browse the created directory in Finder.
• In the "library" subdirectory, the libraries that must be set for the parameter "Skip installation" to "Yes" will be indicated.
• in some cases, usr/local/include will identify the criminal header files that you need to move from Public to Project, or the files you need to change, from the absolute path to the product directory. but this directory (e.g. usr / local / include) changes depending on the structure of your subdirectory

Answer 8

Answer 13 worked for me, but there is one more important thing ( from here). It is necessary to define some files as public (when you select a file in the right pane in the "Target Membership" section), by default it is a "project". "If the files are not defined as public, the archive will be empty