Cycle inside ; building could produce unreliable results: Xcode 10 Error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am trying to move to the new build system when compiling with Xcode 10. However, it gives following error:
Cycle details:
→ Target 'project' : LinkStoryboards
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Target 'project' : ValidateEmbeddedBinary /Users/project/Xcode/DerivedData/project-hgqvaddkhmzxfkaycbicisabeakv/Build/Products/Debug-iphoneos/project.app/PlugIns/stickers.appex
Target 'project' has process command with input '/Users/project/Resources/Info.plist'
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Even after removing the problem file, I get same for another xib/storyboard. How can I solve this error without reverting to the legacy build system?
xcode10 build-system
add a comment |
I am trying to move to the new build system when compiling with Xcode 10. However, it gives following error:
Cycle details:
→ Target 'project' : LinkStoryboards
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Target 'project' : ValidateEmbeddedBinary /Users/project/Xcode/DerivedData/project-hgqvaddkhmzxfkaycbicisabeakv/Build/Products/Debug-iphoneos/project.app/PlugIns/stickers.appex
Target 'project' has process command with input '/Users/project/Resources/Info.plist'
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Even after removing the problem file, I get same for another xib/storyboard. How can I solve this error without reverting to the legacy build system?
xcode10 build-system
add a comment |
I am trying to move to the new build system when compiling with Xcode 10. However, it gives following error:
Cycle details:
→ Target 'project' : LinkStoryboards
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Target 'project' : ValidateEmbeddedBinary /Users/project/Xcode/DerivedData/project-hgqvaddkhmzxfkaycbicisabeakv/Build/Products/Debug-iphoneos/project.app/PlugIns/stickers.appex
Target 'project' has process command with input '/Users/project/Resources/Info.plist'
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Even after removing the problem file, I get same for another xib/storyboard. How can I solve this error without reverting to the legacy build system?
xcode10 build-system
I am trying to move to the new build system when compiling with Xcode 10. However, it gives following error:
Cycle details:
→ Target 'project' : LinkStoryboards
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Target 'project' : ValidateEmbeddedBinary /Users/project/Xcode/DerivedData/project-hgqvaddkhmzxfkaycbicisabeakv/Build/Products/Debug-iphoneos/project.app/PlugIns/stickers.appex
Target 'project' has process command with input '/Users/project/Resources/Info.plist'
Target 'project' has compile command with input '/Users/project/Commons/Components/ScreenshotSharing/ViewController/AppShare.storyboard'
Even after removing the problem file, I get same for another xib/storyboard. How can I solve this error without reverting to the legacy build system?
xcode10 build-system
xcode10 build-system
edited Feb 14 at 22:26
Ben Leggiero
5,19843763
5,19843763
asked Jun 5 '18 at 21:39
Sahil KapoorSahil Kapoor
6,78394773
6,78394773
add a comment |
add a comment |
19 Answers
19
active
oldest
votes
For anybody having an issue with Xcode 10 build system, follow the following steps to fix it:
- In Xcode, go to File->Project/Workspace settings.
- Change the build system to Legacy Build system.
It will resolve the build issue with the new Xcode.
If you want to work with the new build system, then you can find the troubleshooting help from this apple Xcode help page.
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
add a comment |
I was having this issue with Cocoapods. The solution was to clean the build folder re-install all pods, and then rebuild the app. The issue resolved itself that way.
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
add a comment |
Xcode 10's new build system detects dependency cycles in your build and provides diagnostics to help you resolve them. Fixing these dependency cycles improves the reliability of your build, so that the correct products are produced consistently (cycles are a possible cause of needing to delete your derived data). It also improves your incremental build times, as cycles in the build cause something in your build graph to always be out-of-date on each build, making the build re-do work unnecessarily every time you build.
There is documentation on resolving some common types of dependency cycles in Xcode Help: https://help.apple.com/xcode/mac/current/#/dev621201fb0
That said, this cycle diagnostic looks a little odd. It sounds like you were able to resolve it by re-arranging your build phases, but I don't think the diagnostic really explained the problem. If you wouldn't mind, a bug report about improving this diagnostic for this particular case would be very much appreciated. You can file one at https://bugreport.apple.com. Please include all details about your project that you think might be relevant; a sample project that reproduces the issue is ideal, but if you can't attach that, the diagnostic and some idea of the project structure is still helpful.
add a comment |
I fixed my problem by moving the 'Copy Bundle Resources' Build Phase before all my 'Copy Files' & 'Link Binary with Libraries' Build Phases
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
add a comment |
I was having this issue with Cocoapods and found a temporary workaround:
- Install latest version of cocoapods (1.5.3):
sudo gem update cocoapods
- Delete you derived data:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod install
Source here and I'm on Xcode 10 beta 4.
EDIT: now on Xcode 10.0 and still relevant.
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform aClean Build Folder
(and quitting Xcode might help also) before doing steps2.
and3.
.
– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
add a comment |
I was finally able to resolve this by moving Embed App Extensions
script in Build Phases
of main Target to last position.
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
add a comment |
I was facing the same issue: below was the error
Cycle in dependencies between targets 'Pods-MyAppName' and 'RxCocoa';
building could produce unreliable results. This usually can be
resolved by moving the target's Headers build phase before Compile
Sources. Cycle path: Pods-MyAppName → RxCocoa → Pods-MyAppName
I solved it using the below steps:
1). Go to target RxCocoa in Pods-MyAppName project
2) Go to build phases
3) Drag the Headers Phase and move it above the Complile Sources build phase.
This fixed my issue.
Hope it helps!
add a comment |
I had a similar issue with a mixed interaction between Swift, Objective-C and CoreData: in my project (written in Swift) I made use of Core Data's autogenerated Swift classes as well.
But at one point I needed an Objective C class with public properties (defined in its header counterpart) referring the the core data entities.
#import "ProjectName-Swift.h" // this is to import the swift entities into ObjC
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
As soon as I changed the CoreData model, XCode tried to rebuild the classes and I got hung with the indicated cycle build error.
After an initial moment of despair, as I did not have any compile header phases in my project to change the order of, I found out that solution was quite simple:
In the myObjCClass.h
I removed the shared Swift header import statement and changed it with a @class
directive:
@class MyCoreDataClass; // tell the compiler I will import the class definition somewhere else
// the rest stays the same
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
and I moved the #import "ProjectName-Swift.h"
statement into the myObjCClass.m
class definition file.
#import "myObjCClass.h"
#import "ProjectName-Swift.h"
@implementation myObjCClass
@end
And it builded no worries.
add a comment |
In the target's Scheme
, find the label Build
, and ensure that Find Implicit Dependencies
is not checked. These steps may work.
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
add a comment |
Same issue on Version 10.0 beta 3 (10L201y)
and I wanted to have the New Build System.
Problem is had disabled Enable Modules (C and Objective-C)
in Build Settings -> Apple Clang - Language - Modules
After enabling it (set to YES) got rid of the Error.
add a comment |
I've met similar issue when tried to archive my project on Xcode 10.
Here's the detail text:
→ Target 'mytarget': CodeSign /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
○ Target 'mytarget': SetMode u+w,go-w,a+rX /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
Fixed it by setting $(USER)
in mytarget -> Build Settings -> Deployment -> Install Owner
add a comment |
It seems that you need to change the order of the build phases within your Pods targets. For me, moving Headers above the rest worked. You can automate this in your Podfile:
require 'xcodeproj'
post_install do |installer|
installer.pods_project.targets.each do |target|
headers_phase = target.build_phases.find { |p| p.kind_of?(Xcodeproj::Project::Object::PBXHeadersBuildPhase) }
if headers_phase
puts "#{target.name}: Moving Headers build phase to top"
target.build_phases.insert(0, target.build_phases.delete_at(target.build_phases.index(headers_phase)))
end
end
end
add a comment |
My solution was simply to Clean Build Folder then re-build.
add a comment |
Core_Data
I had the same problem and error but mine happened when I "Created NSManagedObject Subclass" for my entity and I faced this error. So if you think your error is same as mine about Core Data what can probably help you (and helped me ) is to:
- click on your Entity in you "xcdatamodel" file
- go to your right bar click on Data Model Inspector
- change "Module" to "Current Product Module"
- and finally, change "Codegen" to "Manual/None"
- clean and build
I think because in other scenarios Xcode creates a file automatically and when we create another one it causes a conflict.
add a comment |
You might be able to fix this here:
File -> Workspace Settings -> Build System: New Build System
add a comment |
I have tried things from this page but the only thing that has helped me was that I made a copy of the target and updated the name of the copy (removed the copy suffix), and deleted the old one, and did pod install afterwards.
add a comment |
My issue had to do with a cyclical dependency between my swift bridging header and my objective c files.
In my objective c header files I had a #import "...-swift.h"
file and then in a couple of my swift files I was including those files with said import and thus causing a cyclical dependency.
This is the StackOverflow that led me to find the solution:
Objective C, Swift Interoperability issue due to circular dependency
How to prevent circular reference when Swift bridging header imports a file that imports Hopscotch-Swift.h itself
EDIT:
I wound up converting the above files to swift and this solved my issue.
add a comment |
I solved this by moving the "Run Script" to the top of the build phases.
add a comment |
Following two options worked for me: File->Project/Workspace settings.
1, Change the build system to "Legacy Build system" in File->Project Settings
2, Edit Scheme and Select "Parallelize Build" option under Build section.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f50709330%2fcycle-inside-building-could-produce-unreliable-results-xcode-10-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
19 Answers
19
active
oldest
votes
19 Answers
19
active
oldest
votes
active
oldest
votes
active
oldest
votes
For anybody having an issue with Xcode 10 build system, follow the following steps to fix it:
- In Xcode, go to File->Project/Workspace settings.
- Change the build system to Legacy Build system.
It will resolve the build issue with the new Xcode.
If you want to work with the new build system, then you can find the troubleshooting help from this apple Xcode help page.
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
add a comment |
For anybody having an issue with Xcode 10 build system, follow the following steps to fix it:
- In Xcode, go to File->Project/Workspace settings.
- Change the build system to Legacy Build system.
It will resolve the build issue with the new Xcode.
If you want to work with the new build system, then you can find the troubleshooting help from this apple Xcode help page.
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
add a comment |
For anybody having an issue with Xcode 10 build system, follow the following steps to fix it:
- In Xcode, go to File->Project/Workspace settings.
- Change the build system to Legacy Build system.
It will resolve the build issue with the new Xcode.
If you want to work with the new build system, then you can find the troubleshooting help from this apple Xcode help page.
For anybody having an issue with Xcode 10 build system, follow the following steps to fix it:
- In Xcode, go to File->Project/Workspace settings.
- Change the build system to Legacy Build system.
It will resolve the build issue with the new Xcode.
If you want to work with the new build system, then you can find the troubleshooting help from this apple Xcode help page.
answered Jun 28 '18 at 18:24
Akshay SunderwaniAkshay Sunderwani
8,04952149
8,04952149
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
add a comment |
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
18
18
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
The whole point of the question is to move to the latest build system.
– Sahil Kapoor
Jun 29 '18 at 6:32
3
3
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
Then you should mention that in question that you don’t want solution with changing the build system. Also, I have mentioned that if you want to work with new build system then you can follow steps given at Xcode support center. Also, provide a valid reason when you downvote. Thanks! @SahilKapoor
– Akshay Sunderwani
Jun 29 '18 at 11:38
1
1
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
Thank you kind stranger. My only interest is getting my build working again to hit a deadline so your answer is exactly what I needed.
– Dan Loughney
Oct 16 '18 at 21:23
2
2
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
This is not an appropriate solution to the problem. The build system should not be changed to Legacy for something this simple.
– Varun Goyal
Feb 1 at 18:44
add a comment |
I was having this issue with Cocoapods. The solution was to clean the build folder re-install all pods, and then rebuild the app. The issue resolved itself that way.
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
add a comment |
I was having this issue with Cocoapods. The solution was to clean the build folder re-install all pods, and then rebuild the app. The issue resolved itself that way.
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
add a comment |
I was having this issue with Cocoapods. The solution was to clean the build folder re-install all pods, and then rebuild the app. The issue resolved itself that way.
I was having this issue with Cocoapods. The solution was to clean the build folder re-install all pods, and then rebuild the app. The issue resolved itself that way.
answered Jun 6 '18 at 17:35
JALJAL
33.5k17122234
33.5k17122234
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
add a comment |
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
1
1
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
This worked for me as well. I did a clean and a pod install.
– Cloud9999Strife
Aug 3 '18 at 12:56
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
In my case, I'd just done a pod install so only had to clean the build folder. This error only came up after I allowed Xcode to update build settings.
– Stonetip
Oct 28 '18 at 19:55
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
Just clean derived data.. no need for all that..
– Nour1991
Mar 19 at 7:43
add a comment |
Xcode 10's new build system detects dependency cycles in your build and provides diagnostics to help you resolve them. Fixing these dependency cycles improves the reliability of your build, so that the correct products are produced consistently (cycles are a possible cause of needing to delete your derived data). It also improves your incremental build times, as cycles in the build cause something in your build graph to always be out-of-date on each build, making the build re-do work unnecessarily every time you build.
There is documentation on resolving some common types of dependency cycles in Xcode Help: https://help.apple.com/xcode/mac/current/#/dev621201fb0
That said, this cycle diagnostic looks a little odd. It sounds like you were able to resolve it by re-arranging your build phases, but I don't think the diagnostic really explained the problem. If you wouldn't mind, a bug report about improving this diagnostic for this particular case would be very much appreciated. You can file one at https://bugreport.apple.com. Please include all details about your project that you think might be relevant; a sample project that reproduces the issue is ideal, but if you can't attach that, the diagnostic and some idea of the project structure is still helpful.
add a comment |
Xcode 10's new build system detects dependency cycles in your build and provides diagnostics to help you resolve them. Fixing these dependency cycles improves the reliability of your build, so that the correct products are produced consistently (cycles are a possible cause of needing to delete your derived data). It also improves your incremental build times, as cycles in the build cause something in your build graph to always be out-of-date on each build, making the build re-do work unnecessarily every time you build.
There is documentation on resolving some common types of dependency cycles in Xcode Help: https://help.apple.com/xcode/mac/current/#/dev621201fb0
That said, this cycle diagnostic looks a little odd. It sounds like you were able to resolve it by re-arranging your build phases, but I don't think the diagnostic really explained the problem. If you wouldn't mind, a bug report about improving this diagnostic for this particular case would be very much appreciated. You can file one at https://bugreport.apple.com. Please include all details about your project that you think might be relevant; a sample project that reproduces the issue is ideal, but if you can't attach that, the diagnostic and some idea of the project structure is still helpful.
add a comment |
Xcode 10's new build system detects dependency cycles in your build and provides diagnostics to help you resolve them. Fixing these dependency cycles improves the reliability of your build, so that the correct products are produced consistently (cycles are a possible cause of needing to delete your derived data). It also improves your incremental build times, as cycles in the build cause something in your build graph to always be out-of-date on each build, making the build re-do work unnecessarily every time you build.
There is documentation on resolving some common types of dependency cycles in Xcode Help: https://help.apple.com/xcode/mac/current/#/dev621201fb0
That said, this cycle diagnostic looks a little odd. It sounds like you were able to resolve it by re-arranging your build phases, but I don't think the diagnostic really explained the problem. If you wouldn't mind, a bug report about improving this diagnostic for this particular case would be very much appreciated. You can file one at https://bugreport.apple.com. Please include all details about your project that you think might be relevant; a sample project that reproduces the issue is ideal, but if you can't attach that, the diagnostic and some idea of the project structure is still helpful.
Xcode 10's new build system detects dependency cycles in your build and provides diagnostics to help you resolve them. Fixing these dependency cycles improves the reliability of your build, so that the correct products are produced consistently (cycles are a possible cause of needing to delete your derived data). It also improves your incremental build times, as cycles in the build cause something in your build graph to always be out-of-date on each build, making the build re-do work unnecessarily every time you build.
There is documentation on resolving some common types of dependency cycles in Xcode Help: https://help.apple.com/xcode/mac/current/#/dev621201fb0
That said, this cycle diagnostic looks a little odd. It sounds like you were able to resolve it by re-arranging your build phases, but I don't think the diagnostic really explained the problem. If you wouldn't mind, a bug report about improving this diagnostic for this particular case would be very much appreciated. You can file one at https://bugreport.apple.com. Please include all details about your project that you think might be relevant; a sample project that reproduces the issue is ideal, but if you can't attach that, the diagnostic and some idea of the project structure is still helpful.
answered Jun 6 '18 at 6:07
Rick BallardRick Ballard
3,89121015
3,89121015
add a comment |
add a comment |
I fixed my problem by moving the 'Copy Bundle Resources' Build Phase before all my 'Copy Files' & 'Link Binary with Libraries' Build Phases
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
add a comment |
I fixed my problem by moving the 'Copy Bundle Resources' Build Phase before all my 'Copy Files' & 'Link Binary with Libraries' Build Phases
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
add a comment |
I fixed my problem by moving the 'Copy Bundle Resources' Build Phase before all my 'Copy Files' & 'Link Binary with Libraries' Build Phases
I fixed my problem by moving the 'Copy Bundle Resources' Build Phase before all my 'Copy Files' & 'Link Binary with Libraries' Build Phases
answered Jun 13 '18 at 7:29
gypsyDevgypsyDev
5071618
5071618
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
add a comment |
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
+1 but I used a slight variation. I did not need to move anything ahead of "Link Binary with Libraries", which I would not do because a new default project in Xcode is not like that. I just moved "Copy Bundle Resources" ahead of "Copy Helper Tools" (which copies some command-line tools and a helper app to Contents/Helpers of the macOS app product). But since the order of these two should make any difference – they are only copying files – it does not make sense. So I filed a bug: 42927301. My modified solution: Swap around various Copy XXX Build Phases until it works :(
– Jerry Krinock
Aug 4 '18 at 7:04
1
1
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
Same for me, I moved my Copy Bundle Resources above the Copy Files phase and presto it works now. I will dupe your bug @JerryKrinock
– Peter N Lewis
Oct 29 '18 at 7:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped.
– Elena
Nov 2 '18 at 15:06
add a comment |
I was having this issue with Cocoapods and found a temporary workaround:
- Install latest version of cocoapods (1.5.3):
sudo gem update cocoapods
- Delete you derived data:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod install
Source here and I'm on Xcode 10 beta 4.
EDIT: now on Xcode 10.0 and still relevant.
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform aClean Build Folder
(and quitting Xcode might help also) before doing steps2.
and3.
.
– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
add a comment |
I was having this issue with Cocoapods and found a temporary workaround:
- Install latest version of cocoapods (1.5.3):
sudo gem update cocoapods
- Delete you derived data:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod install
Source here and I'm on Xcode 10 beta 4.
EDIT: now on Xcode 10.0 and still relevant.
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform aClean Build Folder
(and quitting Xcode might help also) before doing steps2.
and3.
.
– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
add a comment |
I was having this issue with Cocoapods and found a temporary workaround:
- Install latest version of cocoapods (1.5.3):
sudo gem update cocoapods
- Delete you derived data:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod install
Source here and I'm on Xcode 10 beta 4.
EDIT: now on Xcode 10.0 and still relevant.
I was having this issue with Cocoapods and found a temporary workaround:
- Install latest version of cocoapods (1.5.3):
sudo gem update cocoapods
- Delete you derived data:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod install
Source here and I'm on Xcode 10 beta 4.
EDIT: now on Xcode 10.0 and still relevant.
edited Nov 16 '18 at 3:04
answered Jul 26 '18 at 14:27
gabuchangabuchan
3951214
3951214
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform aClean Build Folder
(and quitting Xcode might help also) before doing steps2.
and3.
.
– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
add a comment |
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform aClean Build Folder
(and quitting Xcode might help also) before doing steps2.
and3.
.
– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
1
1
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
this didn't work for me..
– Dan Revah
Dec 7 '18 at 9:48
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform a
Clean Build Folder
(and quitting Xcode might help also) before doing steps 2.
and 3.
.– gabuchan
Dec 10 '18 at 1:55
it happened to me again last week on Xcode 10.1 (10B61) and it still worked. Make sure to perform a
Clean Build Folder
(and quitting Xcode might help also) before doing steps 2.
and 3.
.– gabuchan
Dec 10 '18 at 1:55
Worked like a charm!
– flagman
Jan 10 at 3:52
Worked like a charm!
– flagman
Jan 10 at 3:52
add a comment |
I was finally able to resolve this by moving Embed App Extensions
script in Build Phases
of main Target to last position.
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
add a comment |
I was finally able to resolve this by moving Embed App Extensions
script in Build Phases
of main Target to last position.
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
add a comment |
I was finally able to resolve this by moving Embed App Extensions
script in Build Phases
of main Target to last position.
I was finally able to resolve this by moving Embed App Extensions
script in Build Phases
of main Target to last position.
answered Jun 6 '18 at 4:54
Sahil KapoorSahil Kapoor
6,78394773
6,78394773
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
add a comment |
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-)
– StackUnderflow
Jul 18 '18 at 23:34
add a comment |
I was facing the same issue: below was the error
Cycle in dependencies between targets 'Pods-MyAppName' and 'RxCocoa';
building could produce unreliable results. This usually can be
resolved by moving the target's Headers build phase before Compile
Sources. Cycle path: Pods-MyAppName → RxCocoa → Pods-MyAppName
I solved it using the below steps:
1). Go to target RxCocoa in Pods-MyAppName project
2) Go to build phases
3) Drag the Headers Phase and move it above the Complile Sources build phase.
This fixed my issue.
Hope it helps!
add a comment |
I was facing the same issue: below was the error
Cycle in dependencies between targets 'Pods-MyAppName' and 'RxCocoa';
building could produce unreliable results. This usually can be
resolved by moving the target's Headers build phase before Compile
Sources. Cycle path: Pods-MyAppName → RxCocoa → Pods-MyAppName
I solved it using the below steps:
1). Go to target RxCocoa in Pods-MyAppName project
2) Go to build phases
3) Drag the Headers Phase and move it above the Complile Sources build phase.
This fixed my issue.
Hope it helps!
add a comment |
I was facing the same issue: below was the error
Cycle in dependencies between targets 'Pods-MyAppName' and 'RxCocoa';
building could produce unreliable results. This usually can be
resolved by moving the target's Headers build phase before Compile
Sources. Cycle path: Pods-MyAppName → RxCocoa → Pods-MyAppName
I solved it using the below steps:
1). Go to target RxCocoa in Pods-MyAppName project
2) Go to build phases
3) Drag the Headers Phase and move it above the Complile Sources build phase.
This fixed my issue.
Hope it helps!
I was facing the same issue: below was the error
Cycle in dependencies between targets 'Pods-MyAppName' and 'RxCocoa';
building could produce unreliable results. This usually can be
resolved by moving the target's Headers build phase before Compile
Sources. Cycle path: Pods-MyAppName → RxCocoa → Pods-MyAppName
I solved it using the below steps:
1). Go to target RxCocoa in Pods-MyAppName project
2) Go to build phases
3) Drag the Headers Phase and move it above the Complile Sources build phase.
This fixed my issue.
Hope it helps!
answered Sep 14 '18 at 8:55
NoProbNoProb
404517
404517
add a comment |
add a comment |
I had a similar issue with a mixed interaction between Swift, Objective-C and CoreData: in my project (written in Swift) I made use of Core Data's autogenerated Swift classes as well.
But at one point I needed an Objective C class with public properties (defined in its header counterpart) referring the the core data entities.
#import "ProjectName-Swift.h" // this is to import the swift entities into ObjC
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
As soon as I changed the CoreData model, XCode tried to rebuild the classes and I got hung with the indicated cycle build error.
After an initial moment of despair, as I did not have any compile header phases in my project to change the order of, I found out that solution was quite simple:
In the myObjCClass.h
I removed the shared Swift header import statement and changed it with a @class
directive:
@class MyCoreDataClass; // tell the compiler I will import the class definition somewhere else
// the rest stays the same
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
and I moved the #import "ProjectName-Swift.h"
statement into the myObjCClass.m
class definition file.
#import "myObjCClass.h"
#import "ProjectName-Swift.h"
@implementation myObjCClass
@end
And it builded no worries.
add a comment |
I had a similar issue with a mixed interaction between Swift, Objective-C and CoreData: in my project (written in Swift) I made use of Core Data's autogenerated Swift classes as well.
But at one point I needed an Objective C class with public properties (defined in its header counterpart) referring the the core data entities.
#import "ProjectName-Swift.h" // this is to import the swift entities into ObjC
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
As soon as I changed the CoreData model, XCode tried to rebuild the classes and I got hung with the indicated cycle build error.
After an initial moment of despair, as I did not have any compile header phases in my project to change the order of, I found out that solution was quite simple:
In the myObjCClass.h
I removed the shared Swift header import statement and changed it with a @class
directive:
@class MyCoreDataClass; // tell the compiler I will import the class definition somewhere else
// the rest stays the same
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
and I moved the #import "ProjectName-Swift.h"
statement into the myObjCClass.m
class definition file.
#import "myObjCClass.h"
#import "ProjectName-Swift.h"
@implementation myObjCClass
@end
And it builded no worries.
add a comment |
I had a similar issue with a mixed interaction between Swift, Objective-C and CoreData: in my project (written in Swift) I made use of Core Data's autogenerated Swift classes as well.
But at one point I needed an Objective C class with public properties (defined in its header counterpart) referring the the core data entities.
#import "ProjectName-Swift.h" // this is to import the swift entities into ObjC
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
As soon as I changed the CoreData model, XCode tried to rebuild the classes and I got hung with the indicated cycle build error.
After an initial moment of despair, as I did not have any compile header phases in my project to change the order of, I found out that solution was quite simple:
In the myObjCClass.h
I removed the shared Swift header import statement and changed it with a @class
directive:
@class MyCoreDataClass; // tell the compiler I will import the class definition somewhere else
// the rest stays the same
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
and I moved the #import "ProjectName-Swift.h"
statement into the myObjCClass.m
class definition file.
#import "myObjCClass.h"
#import "ProjectName-Swift.h"
@implementation myObjCClass
@end
And it builded no worries.
I had a similar issue with a mixed interaction between Swift, Objective-C and CoreData: in my project (written in Swift) I made use of Core Data's autogenerated Swift classes as well.
But at one point I needed an Objective C class with public properties (defined in its header counterpart) referring the the core data entities.
#import "ProjectName-Swift.h" // this is to import the swift entities into ObjC
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
As soon as I changed the CoreData model, XCode tried to rebuild the classes and I got hung with the indicated cycle build error.
After an initial moment of despair, as I did not have any compile header phases in my project to change the order of, I found out that solution was quite simple:
In the myObjCClass.h
I removed the shared Swift header import statement and changed it with a @class
directive:
@class MyCoreDataClass; // tell the compiler I will import the class definition somewhere else
// the rest stays the same
@interface myObjCClass : NSObject
@property (nonatomic) MyCoreDataClass*myEntity;
@end
and I moved the #import "ProjectName-Swift.h"
statement into the myObjCClass.m
class definition file.
#import "myObjCClass.h"
#import "ProjectName-Swift.h"
@implementation myObjCClass
@end
And it builded no worries.
answered Nov 2 '18 at 12:09
LookajiLookaji
794419
794419
add a comment |
add a comment |
In the target's Scheme
, find the label Build
, and ensure that Find Implicit Dependencies
is not checked. These steps may work.
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
add a comment |
In the target's Scheme
, find the label Build
, and ensure that Find Implicit Dependencies
is not checked. These steps may work.
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
add a comment |
In the target's Scheme
, find the label Build
, and ensure that Find Implicit Dependencies
is not checked. These steps may work.
In the target's Scheme
, find the label Build
, and ensure that Find Implicit Dependencies
is not checked. These steps may work.
edited Feb 25 at 21:02
Ben Leggiero
5,19843763
5,19843763
answered Jul 26 '18 at 4:37
Nh XuNh Xu
638
638
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
add a comment |
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
When you say "close", do you mean it should have a color and a check mark? Or that it should be empty, without a check mark?
– Ben Leggiero
Feb 14 at 22:36
1
1
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
Hi, @BenLeggiero. "Close" means it should be empty, without a check mark.
– Nh Xu
Feb 25 at 5:44
add a comment |
Same issue on Version 10.0 beta 3 (10L201y)
and I wanted to have the New Build System.
Problem is had disabled Enable Modules (C and Objective-C)
in Build Settings -> Apple Clang - Language - Modules
After enabling it (set to YES) got rid of the Error.
add a comment |
Same issue on Version 10.0 beta 3 (10L201y)
and I wanted to have the New Build System.
Problem is had disabled Enable Modules (C and Objective-C)
in Build Settings -> Apple Clang - Language - Modules
After enabling it (set to YES) got rid of the Error.
add a comment |
Same issue on Version 10.0 beta 3 (10L201y)
and I wanted to have the New Build System.
Problem is had disabled Enable Modules (C and Objective-C)
in Build Settings -> Apple Clang - Language - Modules
After enabling it (set to YES) got rid of the Error.
Same issue on Version 10.0 beta 3 (10L201y)
and I wanted to have the New Build System.
Problem is had disabled Enable Modules (C and Objective-C)
in Build Settings -> Apple Clang - Language - Modules
After enabling it (set to YES) got rid of the Error.
answered Jul 25 '18 at 7:58
vauxhallvauxhall
828711
828711
add a comment |
add a comment |
I've met similar issue when tried to archive my project on Xcode 10.
Here's the detail text:
→ Target 'mytarget': CodeSign /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
○ Target 'mytarget': SetMode u+w,go-w,a+rX /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
Fixed it by setting $(USER)
in mytarget -> Build Settings -> Deployment -> Install Owner
add a comment |
I've met similar issue when tried to archive my project on Xcode 10.
Here's the detail text:
→ Target 'mytarget': CodeSign /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
○ Target 'mytarget': SetMode u+w,go-w,a+rX /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
Fixed it by setting $(USER)
in mytarget -> Build Settings -> Deployment -> Install Owner
add a comment |
I've met similar issue when tried to archive my project on Xcode 10.
Here's the detail text:
→ Target 'mytarget': CodeSign /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
○ Target 'mytarget': SetMode u+w,go-w,a+rX /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
Fixed it by setting $(USER)
in mytarget -> Build Settings -> Deployment -> Install Owner
I've met similar issue when tried to archive my project on Xcode 10.
Here's the detail text:
→ Target 'mytarget': CodeSign /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
○ Target 'mytarget': SetMode u+w,go-w,a+rX /path/to/mytarget.app
○ Target 'mytarget': SetGroup staff /path/to/mytarget.app
Fixed it by setting $(USER)
in mytarget -> Build Settings -> Deployment -> Install Owner
edited Sep 26 '18 at 15:15
answered Sep 25 '18 at 12:46
likecatfoodlikecatfood
377
377
add a comment |
add a comment |
It seems that you need to change the order of the build phases within your Pods targets. For me, moving Headers above the rest worked. You can automate this in your Podfile:
require 'xcodeproj'
post_install do |installer|
installer.pods_project.targets.each do |target|
headers_phase = target.build_phases.find { |p| p.kind_of?(Xcodeproj::Project::Object::PBXHeadersBuildPhase) }
if headers_phase
puts "#{target.name}: Moving Headers build phase to top"
target.build_phases.insert(0, target.build_phases.delete_at(target.build_phases.index(headers_phase)))
end
end
end
add a comment |
It seems that you need to change the order of the build phases within your Pods targets. For me, moving Headers above the rest worked. You can automate this in your Podfile:
require 'xcodeproj'
post_install do |installer|
installer.pods_project.targets.each do |target|
headers_phase = target.build_phases.find { |p| p.kind_of?(Xcodeproj::Project::Object::PBXHeadersBuildPhase) }
if headers_phase
puts "#{target.name}: Moving Headers build phase to top"
target.build_phases.insert(0, target.build_phases.delete_at(target.build_phases.index(headers_phase)))
end
end
end
add a comment |
It seems that you need to change the order of the build phases within your Pods targets. For me, moving Headers above the rest worked. You can automate this in your Podfile:
require 'xcodeproj'
post_install do |installer|
installer.pods_project.targets.each do |target|
headers_phase = target.build_phases.find { |p| p.kind_of?(Xcodeproj::Project::Object::PBXHeadersBuildPhase) }
if headers_phase
puts "#{target.name}: Moving Headers build phase to top"
target.build_phases.insert(0, target.build_phases.delete_at(target.build_phases.index(headers_phase)))
end
end
end
It seems that you need to change the order of the build phases within your Pods targets. For me, moving Headers above the rest worked. You can automate this in your Podfile:
require 'xcodeproj'
post_install do |installer|
installer.pods_project.targets.each do |target|
headers_phase = target.build_phases.find { |p| p.kind_of?(Xcodeproj::Project::Object::PBXHeadersBuildPhase) }
if headers_phase
puts "#{target.name}: Moving Headers build phase to top"
target.build_phases.insert(0, target.build_phases.delete_at(target.build_phases.index(headers_phase)))
end
end
end
answered Oct 2 '18 at 20:27
bcherrybcherry
5,96922335
5,96922335
add a comment |
add a comment |
My solution was simply to Clean Build Folder then re-build.
add a comment |
My solution was simply to Clean Build Folder then re-build.
add a comment |
My solution was simply to Clean Build Folder then re-build.
My solution was simply to Clean Build Folder then re-build.
answered Nov 18 '18 at 19:56
onemoreanimalonemoreanimal
5914
5914
add a comment |
add a comment |
Core_Data
I had the same problem and error but mine happened when I "Created NSManagedObject Subclass" for my entity and I faced this error. So if you think your error is same as mine about Core Data what can probably help you (and helped me ) is to:
- click on your Entity in you "xcdatamodel" file
- go to your right bar click on Data Model Inspector
- change "Module" to "Current Product Module"
- and finally, change "Codegen" to "Manual/None"
- clean and build
I think because in other scenarios Xcode creates a file automatically and when we create another one it causes a conflict.
add a comment |
Core_Data
I had the same problem and error but mine happened when I "Created NSManagedObject Subclass" for my entity and I faced this error. So if you think your error is same as mine about Core Data what can probably help you (and helped me ) is to:
- click on your Entity in you "xcdatamodel" file
- go to your right bar click on Data Model Inspector
- change "Module" to "Current Product Module"
- and finally, change "Codegen" to "Manual/None"
- clean and build
I think because in other scenarios Xcode creates a file automatically and when we create another one it causes a conflict.
add a comment |
Core_Data
I had the same problem and error but mine happened when I "Created NSManagedObject Subclass" for my entity and I faced this error. So if you think your error is same as mine about Core Data what can probably help you (and helped me ) is to:
- click on your Entity in you "xcdatamodel" file
- go to your right bar click on Data Model Inspector
- change "Module" to "Current Product Module"
- and finally, change "Codegen" to "Manual/None"
- clean and build
I think because in other scenarios Xcode creates a file automatically and when we create another one it causes a conflict.
Core_Data
I had the same problem and error but mine happened when I "Created NSManagedObject Subclass" for my entity and I faced this error. So if you think your error is same as mine about Core Data what can probably help you (and helped me ) is to:
- click on your Entity in you "xcdatamodel" file
- go to your right bar click on Data Model Inspector
- change "Module" to "Current Product Module"
- and finally, change "Codegen" to "Manual/None"
- clean and build
I think because in other scenarios Xcode creates a file automatically and when we create another one it causes a conflict.
edited Nov 24 '18 at 9:36
Roy Scheffers
2,278102027
2,278102027
answered Nov 23 '18 at 17:07
Alireza ajAlireza aj
115
115
add a comment |
add a comment |
You might be able to fix this here:
File -> Workspace Settings -> Build System: New Build System
add a comment |
You might be able to fix this here:
File -> Workspace Settings -> Build System: New Build System
add a comment |
You might be able to fix this here:
File -> Workspace Settings -> Build System: New Build System
You might be able to fix this here:
File -> Workspace Settings -> Build System: New Build System
edited Nov 30 '18 at 9:00
Matt Rowles
2,357154473
2,357154473
answered Nov 30 '18 at 8:34
Cheng FeiCheng Fei
338
338
add a comment |
add a comment |
I have tried things from this page but the only thing that has helped me was that I made a copy of the target and updated the name of the copy (removed the copy suffix), and deleted the old one, and did pod install afterwards.
add a comment |
I have tried things from this page but the only thing that has helped me was that I made a copy of the target and updated the name of the copy (removed the copy suffix), and deleted the old one, and did pod install afterwards.
add a comment |
I have tried things from this page but the only thing that has helped me was that I made a copy of the target and updated the name of the copy (removed the copy suffix), and deleted the old one, and did pod install afterwards.
I have tried things from this page but the only thing that has helped me was that I made a copy of the target and updated the name of the copy (removed the copy suffix), and deleted the old one, and did pod install afterwards.
answered Jan 16 at 14:50
Vladimír SlavíkVladimír Slavík
8011224
8011224
add a comment |
add a comment |
My issue had to do with a cyclical dependency between my swift bridging header and my objective c files.
In my objective c header files I had a #import "...-swift.h"
file and then in a couple of my swift files I was including those files with said import and thus causing a cyclical dependency.
This is the StackOverflow that led me to find the solution:
Objective C, Swift Interoperability issue due to circular dependency
How to prevent circular reference when Swift bridging header imports a file that imports Hopscotch-Swift.h itself
EDIT:
I wound up converting the above files to swift and this solved my issue.
add a comment |
My issue had to do with a cyclical dependency between my swift bridging header and my objective c files.
In my objective c header files I had a #import "...-swift.h"
file and then in a couple of my swift files I was including those files with said import and thus causing a cyclical dependency.
This is the StackOverflow that led me to find the solution:
Objective C, Swift Interoperability issue due to circular dependency
How to prevent circular reference when Swift bridging header imports a file that imports Hopscotch-Swift.h itself
EDIT:
I wound up converting the above files to swift and this solved my issue.
add a comment |
My issue had to do with a cyclical dependency between my swift bridging header and my objective c files.
In my objective c header files I had a #import "...-swift.h"
file and then in a couple of my swift files I was including those files with said import and thus causing a cyclical dependency.
This is the StackOverflow that led me to find the solution:
Objective C, Swift Interoperability issue due to circular dependency
How to prevent circular reference when Swift bridging header imports a file that imports Hopscotch-Swift.h itself
EDIT:
I wound up converting the above files to swift and this solved my issue.
My issue had to do with a cyclical dependency between my swift bridging header and my objective c files.
In my objective c header files I had a #import "...-swift.h"
file and then in a couple of my swift files I was including those files with said import and thus causing a cyclical dependency.
This is the StackOverflow that led me to find the solution:
Objective C, Swift Interoperability issue due to circular dependency
How to prevent circular reference when Swift bridging header imports a file that imports Hopscotch-Swift.h itself
EDIT:
I wound up converting the above files to swift and this solved my issue.
edited Jan 25 at 11:54
answered Jan 25 at 3:00
ConstantineConstantine
14639
14639
add a comment |
add a comment |
I solved this by moving the "Run Script" to the top of the build phases.
add a comment |
I solved this by moving the "Run Script" to the top of the build phases.
add a comment |
I solved this by moving the "Run Script" to the top of the build phases.
I solved this by moving the "Run Script" to the top of the build phases.
answered Nov 6 '18 at 19:09
MochaMocha
650315
650315
add a comment |
add a comment |
Following two options worked for me: File->Project/Workspace settings.
1, Change the build system to "Legacy Build system" in File->Project Settings
2, Edit Scheme and Select "Parallelize Build" option under Build section.
add a comment |
Following two options worked for me: File->Project/Workspace settings.
1, Change the build system to "Legacy Build system" in File->Project Settings
2, Edit Scheme and Select "Parallelize Build" option under Build section.
add a comment |
Following two options worked for me: File->Project/Workspace settings.
1, Change the build system to "Legacy Build system" in File->Project Settings
2, Edit Scheme and Select "Parallelize Build" option under Build section.
Following two options worked for me: File->Project/Workspace settings.
1, Change the build system to "Legacy Build system" in File->Project Settings
2, Edit Scheme and Select "Parallelize Build" option under Build section.
answered Mar 12 at 20:30
gsrgsr
42
42
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f50709330%2fcycle-inside-building-could-produce-unreliable-results-xcode-10-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown