Error when used in a project targeting catalyst

[ykphuah]

Once I enable catalyst, building for Mac platform will give me the following errors:

Signing for "FontAwesome.swift-FontAwesome.swift" requires a development team. Select a development team in the Signing & Capabilities editor.

It doesn't do this for any other pod files that I use. Excluding FontAwesome (which needs me to set minimum iOS to 13) works as well, but I am wondering why this pod is so special.

Any ideas?

[mpkempson]

I have the same issue. Bumping for visibility

[palla89]

Same problem here

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[appfrilans]

Need this as well

[X-JackWill]

Same problem. In iOS 16. this won't appear until iOS 16.

I config the developer acount. But I don't know why this happens.

[jbgtmartin]

This issue appeared for me after updating XCode from 13.4.1 to 14.0. I can compile if I select a development team in the FontAwesome.swift-FontAwesome.swift target, but I guess it's not supposed to work like this?

[mzekrallah]

suffering from this issue as well. please fix

[AnthoPakPak]

For anybody facing this, here's the solutions (choose the one you prefer):

• Untick "Automatically manage singing" for FontAwesome.swift-FontAwesome.swift target
• Set your own development team for FontAwesome.swift-FontAwesome.swift target
• (PREFERRED) If you're using Cocoapods and want the fix to persist (meaning you won't have to re-do above steps after each pod install), add following code at the end of your Podfile, and re-run pod install:

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