-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with 64-bit Builds and Xcode 5 GM #1352
Conversation
👍 |
even updating it yourself doesn't seem to work. have all mine set fine and getting the same error. |
Ah, perhaps somebody smarter than us will figure out what is really going on here then |
🙀 I think this means I get to go home early. |
If I recall correctly you need to clear the architectures and let Xcode handle them. I guess that now we know why we got that warning for the Pod targets. I implemented the fix in the past but I had to revert because Xcode 4 was failing the build. |
Xcode actually gives me this warning when I attempt to archive, and then it outright fails with this.
Hoping it's related otherwise I have no idea what it'd be. My app's deployment target is 5.1 through 7.0. |
👍 |
1 similar comment
👍 |
👍 ...and yes, |
If you open your Build Phases you'll also notice that the |
How kind of Apple to surprise us with a brand new architecture a week before they expect to go live with our apps! |
So deleting the |
Can you clarify how you "delete the Architectures build settings"? |
@irrationalfab I don't think it's |
@segiddins you're right 😄 |
Confirmed, updated cocoapod gem, deleted Architectures from each of the Pods and was able to Archive & Submit successfully. |
Confirmed here too. Having the issue with cocoapods |
The only issue that I have with this is that breaks CocoaPods installations with Xcode 4. I am of the idea that we should release can however I would prefer to check with @alloy tomorrow. |
@irrationalfab delivers yet again. You, sir, have saved my bacon. |
@kreeger 🍻 |
As an aside: I was able to fix this by changing the Architecture settings to "Standard architectures (including 64-bit)", which is an option in the drop-down on Build Settings. |
Errors gone after deleting but build still fails with no errors this time (gonna be fun to debug...). Awful nice of Apple to drop a new arch on us at the last minute. |
@sirvine That is the default option, so clearing it is equivalent. @holyprin Try cleaning the project (and ensure that you cleaned the archs for all the targets, and that you are not inhibiting warnings in the Podfile). Failure without errors is very suspicious. |
I found it, seems it's an external library failing in the linker but didn't warn me. compiled libs always bite you in the butt on GM days... |
Confirmed. This fixes the architecture problem. Still waiting on the patch for the cocoapods bundles with archive bug: #1329 |
@alloy An error occurred while installing xcodeproj (0.10.1), and Bundler cannot continue. And I did install the The log file indicated has this
|
I've been able to run the latest builds of Then again, I'm using a Ruby 2.0.0 that's provided by rbenv. I'm pretty sure this is a separate issue anyway. It's not related to Xcode 5 support. |
@ppaulojr @AliSoftware @kreeger Yeah this is a OS X 10.9 + Xcode 5 issue. You need a Xcode developer preview that contains the 10.9 SDK and fix the headers as described in #1108 / https://gist.github.com/goshakkk/5763489. |
Problems with 64-bit Builds and Xcode 5 GM
+1, @irrationalfab Thank you, sir. |
thx! |
I've set the
Is there any other config changes that need to be made? |
@zakdances did you delete the ARCHS build setting (to reset it to its default) too (as explained in this comment and below)? |
.@AliSoftware Yes, still having the same problem. Same error message. In fact, after deleting the build settings for all pods, there is 2 additional clang errors:
and
What else can I try to fix all these errors? |
@zakdances Probably the same problem I'm having then here 😒 |
Even after rolling back to version 0.24.0 and 0.23.0 of Cocoapods, the same errors occur. Nothing will compile. Is there a minimum OSX version or Xcode version that Cocoapods requires that could be an issue? How can I narrow down the cause these errors? |
After manually settings the |
I got this working by manually targeting only armv7 (removed armv7s) from ARCHS in command line build. |
I'm still seeing this issue after trying all of the suggestions on this issue. Pods compiles and runs fine on the simulator, but doesn't run on the device. |
Why build active architecture only for debug builds and thus require the extra Xcode setting in our projects? Why not just have Cocoapods build all architectures for debug like it does for all other configurations? I guess it's faster to build only for the active arch, but this seems complicated an introduces confusion and support issues for cocoapods. Is there a compelling reason not to have cocoapods just build all architectures for all configurations, including debug? Thanks! |
Building for active architecture only is the default for new projects in Xcode 5. |
OK, that's fair then. I'm using this in a project originally created in Xcode 4, so I guess that's why I had the issue then. But I imagine lots of others will have the same problem. Thanks for letting me know. |
@alloy Your FAQ link forwards to http://guides.cocoapods.org/using/faq.html, which doesn't address this issue. |
@getaaron This information should be available in the troubleshooting guide. |
I can try and update it myself, but in the future, Cocoapods should add the
arm64
architecture to the pods when detected