-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Embed Pods Frameworks fails when target has spaces #3754
Comments
Can confirm, I had the exact same problem. |
When I added logging lines it was dying here:
But it was not sending over the all the frameworks over, my build script looked like: https://gist.github.com/orta/94d1c72127738c61cd4a |
Using |
I'm having the same issue with FastImageCache 1.3. I tried that branch @orta recommended and it fails to
Podfile: source 'https://github.com/CocoaPods/Specs'
use_frameworks!
pod 'Helpshift'
pod 'FastImageCache'
pod 'TZStackView', :git => 'https://github.com/soffes/TZStackView.git', :commit => '52b2cd304ce5933ce327dcfca6d37dbd7e247391' |
This is fixed in 0.38, but if you really want to not update CocoaPods - you can be sneaky. |
@Isuru-Nanayakkara that's a separate issue, and the error there is printed:
|
I'm getting this same error in Xcode 7 beta 5 with CocoaPods version 0.38.2. I've tried the suggestions above, but to no avail. Any other suggestions? |
I'm also getting this error with CocoaPods 0.38.2 in XCode 7 beta 5 when trying to build a brand new project where I added Alamofire 2.0.0-beta1. And I don't have any targets with spaces in them.
|
I can confirm the same. I get the exact same error as @sarbogast running CocoaPods 0.38.2 in XCode7 beta 5 and using Alamofire 2.0.0-beta1. I don't have spaces either |
I think I am seeing the same issue, CoccoaPods 0.38.2, XCode7-beta6, Alamofire 2.0.0-beta4, Is there a solution/ workaround? |
Actually I don't think my problem had anything to do with CoccoaPods. I think deleting the derived data for xcode seemed to solve this for me |
Deleting the derived data worked for me too |
I also got the same error in |
@segiddins im having an issue with the same failure as mentioned in your comment, |
Also working for me, thanks @katsuma |
thanks @katsuma, this also fixed it for me |
anybody experiencing this issue with version |
Same with @sgammon im having problem with space on code signing |
I am failing as well with that version. What changed between the old version? |
Falling back to 1.1.1 doesn't seem to solve it. Tried Edit: e.g. (You need to do this for both regular and test targets) |
Yeah I'm having this same issue now too - Xcode 8.1 and Cocoapods 1..2.0.beta.1 |
Arg.. I had to end up upgrading to 1.2.0.beta.1 to fix a pod install 'abort trap 6' error I had after I added a new build configuration after upgrading to macOS Sierra and Xcode 8.1 only to be hit with a new "bug" that was ok previously. Error happens during [CP] Embed Pods Frameworks since my app name has a space in it. This didn't used to be a problem.. |
v1.0.1:
v1.2.0.beta1:
|
I can confirm the single quote wrap mentioned by @freak4pc fixes my problem:
|
@freak4pc I'm confused, where exactly is this code_sign_cmd ? I looked in Target->myTarget->BuildPhases and I'm not seeing it under embed pods framework. Where exactly do I change this? |
For anyone that's wondering, the line:
is located inside: YourProject/Pods/Target\ Support\ Files/Pods-YourProject/Pods-YourProject-frameworks.sh |
|
This issue should be marked as reopened. |
@fulldecent @freak4pc If this is a regression, it should be filed a new issue. |
Looks like a regression to me. New issue: should be reopened. |
Yes seeing it still using latest stable version |
@felixdkatt it's fixed in 1.2.0.beta.3 |
Oh great thanks Ben |
Thanks. |
🌈
I have a project with a target that has spaces on its name, so "Pods-{TARGET}" also contains spaces, which makes Embed Pods Frameworks phase to fail.
I think this was introduced on 0.38.0.beta.1, as this wasn't happening on 0.37.2. I also used
pod deintegrate
to make sure it wasn't an old configuration.Here's the log:
Workaround: If I use the
link_with
directive and create a target with no spaces, the problem doesn't happen.The text was updated successfully, but these errors were encountered: