expo: "Cycle in dependencies between targets 'EXApplication' and 'ExpoModulesCore'" error when "expo run:ios" after running "expo export"

I’m having same issue and none of the above solutions worked for me. XCode 13.1.

cd ios && rm -rf Pods && pod install && cd .. helped for me for some reason. Maybe someone will find it useful

@raphaelmsr @just-a-normal-human not sure if this helps for your guys use case, but for my scenario where I was getting Cycle in dependencies between targets 'EXApplication' and 'ExpoModulesCore' I got it to work by moving the Compile Sources phase of compilation to be before the Headers phase.

I did this by:

1. Opening Pods/Pods.xcodeproj in Xcode
2. Opening the Issue Navigator
3. Selecting the ExpoModulesCore target
4. Selecting Build Phases
5. Moving Compile Sources to be above Headers

I posted a screenshot of how I have ExpoModulesCore configured. Previously, Headers was above Compile Sources

to solve the issue you have to remove the Pods directory.

rm -fr ios/Pods && yarn ios

it happens very often.

Add this to your Podfile:

  post_integrate do |installer|
    update_pod_build_phase_order("./Pods/Pods.xcodeproj", "ExpoModulesCore")
  end

  def update_pod_build_phase_order(xcodeproj_path, target_name)
    puts "Updating build phase order of 'Headers' in #{xcodeproj_path}, #{target_name} \n"
    project = Xcodeproj::Project.open(xcodeproj_path)
    target = project.targets.select { |t| t.name == target_name }.first
    puts "Found target: #{target.name}\n"
    cocoapods_index = target.build_phases.index do |b|
      puts "#{b} , #{b == "HeadersBuildPhase"}"
      b.to_s == "HeadersBuildPhase"
    end
    if cocoapods_index.nil? == false
        puts "#{target_name}: 'HeadersBuildPhase' index was: #{cocoapods_index}, moving to index 1.\n"
        target.build_phases.move_from(cocoapods_index, 1)
    end
    project.save
  end

to summarize - if you encounter this error, you may need to clear and reinstall pods.

Why on earth are people celebrating these comments. Deleting and reinstalling Pods is not the correct solution. If you’re going to make me use the entire bulls*** ecosystem of Expo tools just to use your Secure Storage plugin - the least you can do it ensure it doesn’t build like dirt.

I was facing with this issue in several projects.

Only “solution” that has worked for me was

Create new react-native project (0.68.2) Install expo 45 Do every native module setup step for each library Copy src folder to the new project Test each module, if they are working

Now I have saved tons of hours by not having to do “remove pods, reinstall again, fail, remove pods, reinstall again, hope to not fail, fail” I love my life.

@brentvatne Yeah, I get that. I let my frustration take over my logical thinking. I’ve revoked the previous comments, apologies for the abrupt approach.

I’m having same issue and none of the above solutions worked for me. XCode 13.1.

error: Cycle in dependencies between targets 'EXApplication' and 'ExpoModulesCore'; building could produce unreliable results.
Cycle path: EXApplication → ExpoModulesCore → EXApplication

yarn why expo-modules-core returns only one version:

=> Found "expo-modules-core@0.4.7"