-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Some dependencies¹ NSCocoaErrorDomain Code=260 with archive builds · ⑴ Possibly AFNetworking, possibly constrained to versions around v3.1.0
#2277
Comments
|
Did you solve your problem? I'm having it with AFNetworking, too, in Carthage 0.27. |
|
I personally had to switch back to carthage 0.24 to «fix» the issue |
|
I think this is related to Carthage's use of |
|
Same problem here. |
|
This may be a duplicate of #2220. |
|
anything we can do? this blocks our builds...:( |
|
Please make it sure that you don’t have |
|
the cartfile is super simple: |
|
ah, you mean in AFNetworking itself? |
|
i cannot find any symroot settings in afnetworking. also switching to 3.2 did not help. |
|
I just tried with the carthage 0.28.0 |
|
no dice :(. removed the resolved file, deleted Carthage folder. same versions of XCode and carthage. The latter installed via homebrew. osx is 10.12.6 (sierra). |
|
Can you share a zip of a test project where this happens? |
|
Will do this afternoon. So you mean the Carthage dir after the failure? |
|
ok, i looked at the file system vs the error message. the error is: Failed to write to /Users/daniel/Documents/git/game-on-ios/dependencies/Carthage/Build/iOS/AFNetworking.framework: Error Domain=NSCocoaErrorDomain Code=260 "The file “AFNetworking.framework” couldn’t be opened because there is no such file." UserInfo={NSURL=file:///Users/daniel/Documents/git/game-on-ios/dependencies/Carthage/Checkouts/AFNetworking/build/ArchiveIntermediates/AFNetworking%20iOS/BuildProductsPath/Release-iphoneos/AFNetworking.framework, NSFilePath=/Users/daniel/Documents/git/game-on-ios/dependencies/Carthage/Checkouts/AFNetworking/build/ArchiveIntermediates/AFNetworking iOS/BuildProductsPath/Release-iphoneos/AFNetworking.framework, NSUnderlyingError=0x7fbf73d78d90 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} and indeed, the folder Carthage/Checkouts/AFNetworking/build/ArchiveIntermediates does not exist. that build folder only contains the directories AFNetworking.build and Release-iphonesimulator. |
|
Also seeing this issue, with Xcode 9.3 and Carthage 0.29.0. Only reverting to Carthage 0.24.0 fixes the issue for me, any newer version is not working. As the issue is not repeatable on some machine, it must be related to some local machine settings on my machine as well as @maddanio 's. I will report any finding. |
|
I just found a fix for this issue, it is a rather hidden XCode setting. Please refer to my latest comment on the thread here: #2220 Feel free to validate and close this issue. |
|
So what do i do? Can Carthage fix it? Or does, in my case, AFNetworking need to do this? |
|
@maddanio I'm curious as to why @blender wasn’t able to reproduce the issue, and the answer may be attainable from the build settings from an AFNetworking build on your machine. For you to grab those build settings would require cautiously making and reverting some changes to If you're okay with that, the instructions are below: Instructions to Cautiously Follow, Remembering to Make Redactions on Output
|
archive builds · ⑴ Possibly, constrained to versions around v3.1.0
|
@maddanio apologies if my comment was misleading. The issue you mentioned was happening for me for every Carthage package, not just for AFNetworking. In that case I had to fix my local build setup. If you remove AFNetworking do GCDWebServer and SVProgressHUD compile fine? |
|
But I did nothing on my machine. It’s Carthage downloading from github and building. Still I can check
Gruß!
Daniel Oberhoff
… Am 30.03.2018 um 19:52 schrieb jdhealy ***@***.***>:
@maddanio I'm curious as to why @blender wasn’t able to reproduce the issue, and the answer may be attainable from the build settings from an AFNetworking build on your machine.
For you to grab those build settings would require cautiously making and reverting some changes to ~/Library/Preferences/com.apple.dt.Xcode.plist, and then cautiously redacting some environment variables (which all get output) from the carthage output. (Wish there was a better way…)
If you're okay with that, the instructions are below:
Instructions to Cautiously Follow, Remembering to Make Redactions on Output
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Oh, you are saying those settings may be system wide? How evil...another reason to despise Xcode...
Gruß!
Daniel Oberhoff
… Am 30.03.2018 um 19:52 schrieb jdhealy ***@***.***>:
@maddanio I'm curious as to why @blender wasn’t able to reproduce the issue, and the answer may be attainable from the build settings from an AFNetworking build on your machine.
For you to grab those build settings would require cautiously making and reverting some changes to ~/Library/Preferences/com.apple.dt.Xcode.plist, and then cautiously redacting some environment variables (which all get output) from the carthage output. (Wish there was a better way…)
If you're okay with that, the instructions are below:
Instructions to Cautiously Follow, Remembering to Make Redactions on Output
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@maddanio I did nothing either, still the setting was set to "Legacy" when I went checking. Maybe it's some setting that was kept from an older XCode version, I also use the beta versions every now and then. I honestly do not know why it was not set to the default. |
|
having the same issue on 0.29.0, Xcode 9.4, blank new project. The resolution of #2220 doesn't help. Only switching back to 0.25.0 helps. |
archive builds · ⑴ Possibly, constrained to versions around v3.1.0archive builds · ⑴ Possibly AFNetworking, possibly constrained to versions around v3.1.0
|
@kas-kad, would you be willing to (cautiously) share your build settings? (If you’re using Xcode’s legacy build system, otherwise those instructions aren’t applicable.) That would help us greatly in diagnosing and reproducing the issue. |
|
@jdhealy I reproduced the issue on Carthage 0.30.1. Here are the logs https://gist.github.com/kas-kad/beefae3c83fa060db0cbe39b0f9e3510/raw/4717f84d5320bd4c355292f5ab434be4b70abdcc/gistfile1.txt |
|
@kas-kad infobip/mobile-messaging-sdk-ios has SYMROOT set (here and here). See @ikesyo’s comment: #2277 (comment) I was able to build correctly with Carthage v0.29.0 after removing those lines, When you mentioned “blank new project”: was that a framework that you created where you saw the |
|
@jdhealy removing SYMROOT setting helped me. Thanks! |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
am i the only one? now (osx 10.13.6, XCode 10.0) it happens on every package. |
|
ah, got it, it was the derived data legacy setting. can anyone explain to me what that derived data actually is? |
|
So is there an easy answer to this problem? I am unable to update my Dropbox SDK via Carthage because of this error. @maddanio what did you have to do to get it to work? |
|
@bsabiston, did you read through @AlessandroMulloni’s resolution to this from #2220 mentioned above? |
|
@jdhealy I see that, but my Derived Data build location is already set to 'Unique' ... |
|
Clearing Xcode State is the one usually |
|
Can we all agree that a (badly done) globally strateful buildsystem is a bad idea? |
|
@bsabiston Update to the latest Carthage version: 0.31.2. It worked for me. |
carthage version: 0.26.2xcodebuild -version: Xcode 9.1 Build version 9B55--no-build? yes--no-use-binaries? no--use-submodules?--cache-builds?Cartfile
Carthage Output
The text was updated successfully, but these errors were encountered: