Answer: Updating CocoaPods build phase ordering after pod install

[maxheld]

Hello everyone,

@pietrocaselani and I needed to update the order of the build phases after pod install was run. We are currently migrating our project to support Tuist and ran in to a problem when migrating one specific project. After generating the project with Tuist and running pod install we realised that the generated [CP] Embed Pods Frameworks build-phase in our Tests target was appended to the very end, which caused a build error. This was because it was carried out after a phase that depended on it. The following is a ruby function for the Podfile to update the ordering of the build phases after everything is configured by CocoaPods.

This utilises the post_integrate phase of CocoaPods. It is important that you do this in the post_integrate and not the post_install since there not all changes have been saved to disk.

This might not be the best ruby code and feel free to tweak it to suit your needs. We chose the index 3 but you can probably do something more fancy by inserting before a specific phase.

We hope it helps!

require 'xcodeproj'


def update_pod_build_phase_order(xcodeproj_path, target_name)
     puts "Updating build phase order of '[CP] Embed Pods Frameworks' 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 { |b|
         name = b.name if b.respond_to? :name
         name == "[CP] Embed Pods Frameworks"
     }
     if cocoapods_index.nil? == false
         puts "#{target_name}: '[CP] Embed Pods Frameworks' index was: #{cocoapods_index}, moving to index 3.\n"
         target.build_phases.move_from(cocoapods_index, 3) # move further to the top
     end
     project.save
end


post_integrate do |installer|
    update_pod_build_phase_order("./SomeFramework/SomeFramework.xcodeproj", "SomeFrameworkTests")
end

Thanks to @pepibumur for the idea to use Pod hooks!

[VorkhlikArtem]

Hello @maxheld and everyone,
I've come up with a new clever and elegant solution over such cycle error during build.

Just add this empty pre-script in unitTest Target's scripts in your manifest Project.swift:
.pre(script: " ", name: "[CP] Embed Pods Frameworks")

And after tuist generate -n && pod install you will get a build phase [CP] Embed Pods Frameworks above in your unitTest build phases.

This is my full troubleshooting over it: #5989. Please check it out
I hope I helped you and others who come across this problem