Cycle inside ; building could produce unreliable results: Xcode Error

Question

I am trying to move to the new build system when compiling with Xcode 10. However, it gives the 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 the same for another xib/storyboard. How can I solve this error without reverting to the legacy build system?

I had similar error and got it fixed by deleting 'derived data' and cleaning project. This worked like a charm to me! — Jayprakash Dubey, Sep 16 '19 at 09:44

score 55 · Answer 1 · answered Jun 28 '18 at 18:24

55

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 Sunderwani

12,428
8
29
52

82

The whole point of the question is to move to the latest build system. – Sahil Kapoor Jun 29 '18 at 06:32
5

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
2

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
10

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 01 '19 at 18:44
1

Do NOT follow these instructions. This is incorrect. There's a hint in the name: "Legacy" - in fact, it's been deprecated and no longer supported going forward. – strangetimes Jun 22 '22 at 10:08

score 51 · Answer 2 · answered Jun 06 '18 at 17:35

51

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 06 '18 at 17:35

JAL

41,701
23
172
300

2

This worked for me as well. I did a clean and a pod install. – Cloud9999Strife Aug 03 '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
had the issue with Alamofire. Did a 'Clean Build Folder' without reinstalling any cocoa pods and worked fine – kite_n_code Sep 14 '20 at 06:11
How do you clean the build folder? – rsedlr Jan 13 '23 at 10:51

score 47 · Answer 3 · edited Aug 09 '19 at 08:02

In fact, you only need to pay attention to Xcode's prompt This usually can be resolved by moving the target's Headers build phase before Compile Sources, and then you can do it.

When I encountered this problem, Xcode prompts me:

:-1: Cycle inside XXXX; building could produce unreliable results. This usually can be resolved by moving the target's Headers build phase before Compile Sources.
Cycle details:
→ Target 'XXXX': LinkStoryboards
○ Target 'XXXX: Ditto Path/XXXX-Swift.h /Path/XXXX-Swift.h
○ Target 'XXXX has compile command for Swift source files
○ That command depends on command in Target 'XXXX: script phase “Run Script”

I only did one thing and solved the problem perfectly:

Select Target and then select Build Phase to move the Run Script to the front of Compile Sources.

Run, compiled successfully.

The principle is simple, just change the compilation order.

Xcode 10.2 & Swift 5

this works but only once and then in the next build command, the issue comes back. — Swati, Nov 25 '19 at 05:52
Thanks, that works for me. I used R.swift and this step was in "Installation" but i missed it. — Vladyslav Shmatok, Aug 11 '21 at 21:18

score 33 · Answer 4 · answered Jun 13 '18 at 07:29

33

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 07:29

gypsyDev

1,232
1
14
22

+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 04 '18 at 07:04
2

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 07:58
For me, the problem was with Embed Frameworks dependencies, so I moved Embed Frameworks above Copy Bundle Resources, and it helped. – Elena Nov 02 '18 at 15:06

gabuchan · Answer 5 · 2018-11-16T03:04:09.320

25

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 03:04

answered Jul 26 '18 at 14:27

gabuchan

785
1
7
18

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 01:55
Worked like a charm! – flagman Jan 10 '19 at 03:52

score 19 · Answer 6 · answered Jun 06 '18 at 06:07

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.

score 17 · Answer 7 · answered Nov 02 '18 at 12:09

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.

Wow, thanks so much. Been struggling all night with this, but when I thoroughly implemented this suggestion, the problem was fixed! — Erik van der Neut, Sep 21 '19 at 23:37

score 15 · Accepted Answer · answered Jun 06 '18 at 04:54

15

I was finally able to resolve this by moving Embed App Extensions script in Build Phases of main Target to last position.

answered Jun 06 '18 at 04:54

Sahil Kapoor

11,183
13
64
87

Got this error in Xcode 10.0 beta 4 (10L213o) – this workaround solved it :-) – StackUnderflow Jul 18 '18 at 23:34
how to do that ? can you explain it step by step ?, basically, I have a extension for Siri kit in it and can not run application on simulator but it work on the device – Sultan Ali Jun 11 '21 at 12:56

score 11 · Answer 9 · answered Nov 18 '18 at 19:56

11

My solution was simply to Clean Build Folder then re-build.

answered Nov 18 '18 at 19:56

onemoreanimal

183
2
5

Amazing how nobody rated on this solution. Simple but it's gotta be the first thing we should try before going deeper into the issue. – Hoon Sep 20 '19 at 14:55
Yep, this fixed it for me – Steven Matthews May 14 '21 at 01:13
This worked for me - I'm currently on Xcode 13 and 'Clean Build Folder' can be found under the main 'Product' menu option. – Andy Duncan Feb 16 '22 at 10:03
4

This is not a solution as it keeps happening. – Marcus Ziadé Apr 14 '22 at 08:41

score 7 · Answer 10 · edited Feb 25 '19 at 21:02

7

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 '19 at 21:02

Ky -

30,724
51
192
308

answered Jul 26 '18 at 04:37

Nh Xu

123
8

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? – Ky - Feb 14 '19 at 22:36
1

Hi, @BenLeggiero. "Close" means it should be empty, without a check mark. – Nh Xu Feb 25 '19 at 05:44
This solved the problem for me, I unchecked this from the Scheme build tab for the main target (Xcode 13.3). – Kendall Helmstetter Gelner Mar 17 '22 at 23:34
Followup: With that unchecked it would not build attached Framework I had included in the project. So then I cleaned the build folder, re-checked it... and the error message was gone. – Kendall Helmstetter Gelner Mar 17 '22 at 23:43

score 7 · Answer 11 · answered Sep 14 '18 at 08:55

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!

score 4 · Answer 12 · answered Dec 13 '21 at 14:45

4

I have the same issue with Cocoapods.

Firstly, remove pods:

rm -rf ios/Pods

then install pods again:

cd ios && pod install && cd ..

Then run your app, it should works now.

answered Dec 13 '21 at 14:45

karolkarp

271
2
7

likecatfood · Answer 13 · 2018-09-26T15:15:49.990

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

Constantine · Answer 14 · 2019-01-25T11:54:38.923

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.

score 3 · Answer 15 · answered May 24 '21 at 21:13

The best temporary fix I've found (until you resolve the root problem) is to make a simple change to the source code (even something as trivial as adding a new line) then trying again. I find that making even a whitespace change is enough to allow it to build again. However, this is definitely temporary as it will likely happen again after a few tries.

This is better than cleaning the build folder (which I found to also be temporary) since it's much quicker to make a whitespace change and rebuild, than to clean the build folder and rebuild (especially on larger projects).

It's really terrible, but this does actually work :( – Bek Nov 13 '21 at 22:23 — Bek, Nov 13 '21 at 22:23

score 2 · Answer 16 · answered Oct 02 '18 at 20:27

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

score 2 · Answer 17 · edited Nov 30 '18 at 09:00

2

You might be able to fix this here:

File -> Workspace Settings -> Build System: New Build System

edited Nov 30 '18 at 09:00

Matt Rowles

7,721
18
55
88

answered Nov 30 '18 at 08:34

SepCode

63
9

score 1 · Answer 18 · answered Jul 25 '18 at 07:58

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.

score 1 · Answer 19 · edited Jun 20 '20 at 09:12

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.

score 1 · Answer 20 · answered Apr 23 '19 at 06:09

Xcode 10.2.1/Unit Test Target. My unit test target is independent of host target to improve building time. Solve it by uncheck Find Implicit Dependencies in Scheme - Build options, As i specify all dependencies in Build Settings - Compile Sources.

score 1 · Answer 21 · answered Jul 02 '20 at 05:38

1

Xcode: 11.3.1 Target: XCUITest target

Run command to clean build folder : rm -rf ~/Library/Developer/Xcode/DerivedData/*
Change workspace settings: Select Legacy Build System

answered Jul 02 '20 at 05:38

Kshama Singh

294
2
4

score 0 · Answer 22 · answered Jan 16 '19 at 14:50

0

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 '19 at 14:50

Vladimír Slavík

1,727
1
21
31

score 0 · Answer 23 · answered May 03 '20 at 19:40

0

I faced this problem after updating Xcode to version 11.4. Downgrading to 11.2.1 fixed it.

answered May 03 '20 at 19:40

Deepseey

11
1

same here. downgrade from XCode 13.3 to 13.2 helped – Laufwunder Mar 25 '22 at 09:09

score 0 · Answer 24 · answered Sep 08 '21 at 09:14

Had this problem for a while as well. Added the following block at the end of the podfile (this will also get rid of some warnings):

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.deployment_target = ios_version
    target.build_configurations.each do |config|
      config.build_settings['IOS_DEPLOYMENT_TARGET'] = 'iOS ' + ios_version
    end
  end
end

I also moved use_frameworks! to the root of the Podfile.

score 0 · Answer 25 · answered Feb 11 '22 at 06:51

0

In my case,

Removed all pods and reinstall resolved the error

Remove Pods directory in ios folder
pod install

answered Feb 11 '22 at 06:51

Harshan Morawaka

710
8
6

score 0 · Answer 26 · answered Apr 12 '22 at 11:51

0

Only for Expo

expo prebuild --clean
cd ios
pod install
yarn ios

answered Apr 12 '22 at 11:51

Daniel Danielecki

8,508
6
68
94

score 0 · Answer 27 · answered Jul 17 '22 at 11:53

0

if you are developing on React-Native, it was the best way for me.

cd ios && rm -rf Pods && pod install && cd ..

answered Jul 17 '22 at 11:53

lestonz

149
4

score 0 · Answer 28 · answered Jul 21 '22 at 06:09

0

cd ios && rm -rf Pods && pod install && cd ..

This worked for me.

answered Jul 21 '22 at 06:09

Muhammad Talha

719
1
4
9

score 0 · Answer 29 · answered Jun 08 '23 at 22:54

I know the original question was asking about pure iOS, but if anyone is running into this issue when trying to run native code with Flutter, try the following:

Run flutter clean in terminal or from the Android Studio menus
Clean your build folder in XCode (Product -> Clean Build Folder)
Comment out every bit of native code that you've added to your main application class that references other files.
Comment out everything except #import "GeneratedPluginRegistrant.h" in your bridging header file ([project name]-Bridging-Header.h by default I think)
Target a simulator and run the app from XCode
Uncomment everything you commented out in steps 3 and 4

That's been fixing it for me.

score -1 · Answer 30 · edited Jul 15 '20 at 18:41

-1

In the project pane on the LHS, for your build products, don't select them in the list for Target membership in the RHS pane.

edited Jul 15 '20 at 18:41

Marcello B.

4,177
11
45
65

answered Jul 15 '20 at 17:56

user10658782

21
7

score -3 · Answer 31 · answered Mar 12 '19 at 20:30

-3

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 '19 at 20:30

gsr

5
2

1

That's not related. Modern build system wouldn't cause this. – Raptor Aug 09 '19 at 08:06

Cycle inside ; building could produce unreliable results: Xcode Error

31 Answers31

Core_Data

Linked