skip to Main Content

I’m getting this error when trying to run pod install after adding a Share Extension to my Flutter iOS project:

CopyArgumentError - [Xcodeproj] Unable to find compatibility version string for object version `70`.

Environment:

  • CocoaPods: 1.16.2
  • Xcode: 16.1
  • macOS: 15.0.1
  • Flutter project

My Podfile:

rubyCopyENV['COCOAPODS_DISABLE_STATS'] = 'true'

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

platform :ios, '13.0'

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

target 'Share Extension' do
  use_frameworks!
  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

Steps to reproduce:

  • Working Flutter iOS project with pods installed
  • Added Share Extension target in Xcode
  • Added Share Extension target to Podfile
  • Run pod install -> Error occurs

Things tried:

  • Deleting Pods/, Podfile.lock, Runner.xcworkspace
  • Different Podfile configurations
  • pod deintegrate and reinstall
  • Removing and re-adding Share Extension
  • Downgrading CocoaPods

The project works fine without Share Extension, I’ve removed it and added it multiple tiles. Any ideas how to resolve this?

2

Answers


  1. Chosen as BEST ANSWER

    I found an answer here: https://github.com/CocoaPods/CocoaPods/issues/12671#issuecomment-2445304215

    When adding an extension it changes your objectVersion to 70, so I needed to change it back


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