skip to Main Content

Cycle in dependencies between targets ‘Unity-iPhone’ and ‘UnityFramework’; building could produce unreliable results. This usually can be resolved by moving the target’s Headers build phase before Compile Sources.
Cycle path: Unity-iPhone → UnityFramework → Unity-iPhone

Received with M1 Mac, while trying to build to device from Xcode 13.3

4

Answers


  1. Chosen as BEST ANSWER

    To solve the issue, on Xcode, you need to go to Build Phases -> UnityFramework, and make sure the Headers is listed above the Compile Sources.

    Xcode Screenshot


  2. Changing build order in Xcode from ‘Manual order’ to ‘Dependency order’ may help.

    enter image description here
    enter image description here

    Login or Signup to reply.
  3. Running in Terminal

    defaults write com.apple.dt.XCBuild EnableSwiftBuildSystemIntegration 1
    

    To enable the new build system solved the issue for me.

    Login or Signup to reply.
  4. Move Headers above Compile Sources fixed the error. Please see the image for reference. I have referenced the following Xcode 13.3 Build Failed because of Cycle in Dependencies between targets libsignal-protocol-swift

    enter image description here

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search