Question 68182 in IOS Swift Question posted in
The official documentation can be found here.

Xcode 14 needs selected Development Team for Pod Bundles – Ios swift

XCode image indicating error for lack of required development team

Both projects won’t build with the Xcode 14 beta because of no selected Development Team. Both times it’s the target with the blue lego icon (Bundles I suppose?)

It seems that in earlier versions of Xcode the Team also wasn’t set but it hasn’t lead to a build error.

Would it be wrong to select my own development team here?

Tags:

6

Answers


  1. Chosen as BEST ANSWER
    0

    This post_install script in podfile fixed it. As it seems setting the own developer team is necessary. Replace Your Team ID with the TeamID of your project.

    post_install do |installer|
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings["DEVELOPMENT_TEAM"] = "Your Team ID"
         end
    end
  end
end

  2. 0

    I prefer the below code so you not need to sign every individual package and it is easy when you are using multiple signing teams.

    post_install do |installer|

    installer.pods_project.targets.each do |target|
      if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
        target.build_configurations.each do |config|
            config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end

  end
    Login or Signup to reply.
  3. 0

    My problem was flutter.h not found, google sign in (as above) and webview. This few lines worked if it helps :

    post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
  installer.generated_projects.each do |project|
    project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings["DEVELOPMENT_TEAM"] = "developer code"
      end
    end
  end
end
    Login or Signup to reply.
  4. 0

    In case there is someone needs to know the correct structure of the PodFile

    # Uncomment the next line to define a global platform for your project
# platform :ios, '12.0'


target 'APPTarget' do
    # Comment the next line if you're not using Swift and don't want to use dynamic frameworks
    use_frameworks!
       
    # Your packages goes here

end
 
# Disable signing for pods
post_install do |installer|
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
         end
    end
  end
end
    Login or Signup to reply.
  5. 0

    If you’re experiencing errors with a particular framework, you can manually replace the problematic Pods. To do so, add the debug and release file "CODE_SIGNING_ALLOWED = NO" in the Support Files section located below.
    This is sample

    Login or Signup to reply.
  6. 0

    If you have different signing certificates for different schemes and don’t need the pods signed, you can leave the Team in Xcode to none with the Automatically manage signing checked by default.

    Then add the following config.build_settings… lines to the post_install step in your Pod file, example:

    post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            
            # disable code signing for pods
            config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
            config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
            config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
        end
    end
end
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search