18

I recently started using Xcode 7 GM. When I archive my project, I get a generic Xcode archive instead of an iOS archive.

I'ved tried pretty much all the following:

I compared the contents of a previous successful archive and a different folder structure for some components:

  • Swift libraries are inside a sub folder
  • The app extension is outside of the .app package
  • The info.plist is missing keys

enter image description here

Has anyone else encountering this problem? If so, did you solve and how?

Edit

We are using Cocoapods 0.38.2

Improve this question
12
  • Are you using CocoaPods? Commented Sep 11, 2015 at 12:57
  • Yes, I should have mentioned this, we are using 0.38.2 Commented Sep 11, 2015 at 12:58
  • I have similar problem with creating iOS archive but version 0.38.2 should be ok. But still you could look into issue, mainly Products directory includes usr/local/include because it shouldn't. Commented Sep 11, 2015 at 13:03
  • @LiborZapletal thanks for the tip, I will look into that issue. Commented Sep 11, 2015 at 13:14
  • 1
    I just tried using Cocoapods 0.39 beta 4 and it seems to have fixed my issue. Commented Sep 11, 2015 at 13:15

5 Answers 5

Reset to default
14

I add the same problem : an old Xcode project, Xcode 7 (not the GM, the App Store version) and Cocoapods. I have been tinkering a lot, tried Cocoapds 0.39 b3 and b4 without success, changed params in Build Settings, but finally - for me - the problem was shown by mrezk in https://github.com/CocoaPods/CocoaPods/issues/4021 :

Missing ApplicationProperties in Info.plist

As I'm not used to tinker with Info.plist and these keys, I've found in the Apple Dev forums a very useful answer : https://forums.developer.apple.com/thread/17063

In summary, for info.plist newbies like me ;) :

  1. Archive your project
  2. Organizer will show a Generic Xcode Archive
  3. Right Click, Show in finder
  4. Right Click, Show Package Contents
  5. Open the Info.plist file in a XML editor
  6. As mochs indicates, add these lines in the section :
 <key>ApplicationProperties</key> <dict> <key>ApplicationPath</key> <string>Applications/<<APP_NAME>>.app</string> <key>CFBundleIdentifier</key> <string><<BUNDLE_IDENTIFIER>></string> <key>CFBundleShortVersionString</key> <string><<YOUR_MARKETING_NUMBER>></string> <key>CFBundleVersion</key> <string><<YOUR_BUILD_NUMBER>></string> <key>SigningIdentity</key> <string>iPhone Distribution: <<CERTIFICATE_NAME>> (<<CERTIFICATE_ID>>)</string> </dict>

and replace the tags with your own values.

Save, close Xcode, double click the archive : it should open in the Organizer as a iOS Type Archive.

Thanks to mrezk and mochs for the solution.

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

8 Comments

And, I can confirm first hand that the archive receives a 'Submission Successful' when uploaded to the App Store.
I had the same exact issue, and this also resolved the behavior for me.
This fixed it for me too! Nice job!
How do I fix my project so that future builds don't all have this same problem too
I hope they'll fix Xcode 7 soon, seems a problem when the project is archived
|
4

OP here. The members of my team all tried Cocoapods' beta and it fixed the problem for us. Therefore I'm going to accept my own answer.

Although it might fix the problem, I believe Christian Navelot's answer to not be scalable and certainly not manageable within a team.

Also, all of us tried using the cp beta without removing the Copy Pod Resources build phase. This means that I won't be accepting Todd Anderson's answer either.

We are not using static libraries either, we are using frameworks (aka use frameworks! inside the Podfile).

Thanks to all for contributing to this question. Looks like we all got put into the same boat by Xcode 7! Cheers!

Improve this answer

Comments

3

In my case clearing the "Installation Directory" build setting in all static libraries fixed the issue. It was set to "/usr/local/lib" before.

When using "Save Built Product" as export method the Products folder got these sub directories. That's what pointed me in this direction.

I'm using cocoapods 0.38.2.

Improve this answer

1 Comment

Worked for me in addition to set "Skip install" to NO in the Pods Build settings.
0

The other answers mentioned here were temporary fixes, but each required manual effort, either after every archive or after every pod install.

The new, better solution, is to update cocoapods to the latest version and remove your 'Copy Pod Resources' build phase from each app extension.

See https://github.com/CocoaPods/CocoaPods/issues/4021 for more information.

Improve this answer

3 Comments

Thanks for contributing. I will retest this this week and close this question once and for all if all works out as expected! Cheers!
Actually the latest version (0.39.x) was the problem for me. As the link you posted points out, this is an issue with the latest betas. I completely uninstalled them and rebuilt everything with 0.38.2, which worked. But thanks for posting the link :)
I never use the cocoapods betas and was running into this issue with both .38 and .39, so maybe there was something else going on too.
0

I had a similar issue with XCode7.1.1 and an app project with WatchKit Extension. I fixed the issue by the following step

  • Open Build Settings of my app target and set NO to "Skip Install".

  • Open Build Settings of my WatchKit Extension target and set YES to "Skip Install"

  • Open Build Settings of my WatchKit App target and set YES to "Skip Install"

Then I could make iOS archive.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.