Unable to build with XCode 14.0

[alois-beto]

Description

XCode 14.0 is released since yesterday, and I have the following error while building a fresh app on a physical device:

[...]/ios/Pods/Pods.xcodeproj error project: Signing for "React-Core-AccessibilityResources" requires a development team. Select a development team in the Signing & Capabilities editor.

Is react-native ready for XCode 14?

Version

0.70.0

Output of npx react-native info

System:
OS: macOS 12.5.1
CPU: (10) arm64 Apple M1 Pro
Memory: 6.53 GB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
Yarn: Not Found
npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
Watchman: 2022.08.29.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8815526
Xcode: 14.0/14A309 - /usr/bin/xcodebuild
Languages:
Java: 11.0.16.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.0 => 0.70.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps to reproduce

• Create a fresh react-native app with npx react-native init MyApp
• Open XCode and try to build the app on a real device

Snack, code example, screenshot, or link to a repository

https://github.com/BeTomorrow/react-native-file-logger/tree/master/example

[Thanaen]

I also tried to compile the application in "any device" mode (so not specifically for a physical device), and I get the same error in XCode 14.

Manually selecting a team for this pod seems to solve the problem.
However, I am not sure if this workaround has any side effects.

[almeidabbm]

I also tried to compile the application in "any device" mode (so not specifically for a physical device), and I get the same error in XCode 14.

Manually selecting a team for this pod seems to solve the problem. However, I am not sure if this workaround has any side effects.

I tried setting the team manually and was able to build the app. But somehow the globals declared in babel.config.js failed with ReferenceError: Can't find variable: <variable_name>. I had this issue with __scanCodes from https://github.com/rodgomesc/vision-camera-code-scanner.

As expected reverting XCode to version 13.4.1 fixed all of the above.

[pnthach95]

I use this script and it works

[fabiendem]

From #34673 (comment).
What does CODE_SIGNING_ALLOWED do? Isn't it needed?

[danilobuerger]

See CocoaPods/CocoaPods#11402

[Isaccobosio]

I use this script and it works

Does it work even for react-native apps?
My podFile has this line at the end

post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

How can I merge with that script?

[pnthach95]

How can I merge with that script?

Replace with this

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(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

[relez]

My workaround was to specify the TEAM_ID, my lines looks like this:

post_install do |installer|
  react_native_post_install(installer)
  __apply_Xcode_12_5_M1_post_install_workaround(installer)
  # Add these lines for Xcode 14 builds
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings["DEVELOPMENT_TEAM"] = "TEAM_ID"
        end
    end
  end
  # End of added lines
end

I hope it helps!

[pinokyov]

I solved this problem select development team.

[hakansaglam29]

How can I merge with that script?

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
    installer.pods_project.build_configurations.each do |config|
        config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
    end
  end

you can change your script also like this.

[sunchanras]

@hakansaglam29 I got

How can I merge with that script?

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
    installer.pods_project.build_configurations.each do |config|
        config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
    end
  end

you can change your script also like this.

I got no bitcode error on production build with bitcode enable.

[hugozerken]

same issue here, so how is the effection about setting CODE_SIGNING_ALLOWED = 'NO'

[Nerotox]

My workaround was to specify the TEAM_ID, my lines looks like this:

post_install do |installer|
  react_native_post_install(installer)
  __apply_Xcode_12_5_M1_post_install_workaround(installer)
  # Add these lines for Xcode 14 builds
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings["DEVELOPMENT_TEAM"] = "TEAM_ID"
        end
    end
  end
  # End of added lines
end

I hope it helps!

Worked perfectly thanks!

If anyone else isn't sure where to get his team ID, it can be found on the apple developer website https://developer.apple.com/account/#/membership under the menu "Certificates, Identifiers & Profiles" and then look at the top right under your account name.

[davidking1234]

When implementing this fix, I am getting the following error:
"undefined method `react_native_post_install' for #Pod::Podfile:0x00007fea76758c18"

Is there something else we have to do to get that method to work?

Thanks in advance!

[breezertwo]

@Nerotox

For me the string from the page would't be recognized by Xcode:
I needed my DEVELOPMENT_TEAM id from project.pbxproj file --> looked like this: 0A11BC2345

[christianrank]

I tried adding the fix mentioned here to the Podfile, and it worked locally.

But on the CI running on App Center for release builds, I am now getting this error:
/Users/runner/work/1/s/ios/Pods/Pods.xcodeproj: error: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "XXX" with a private key was found. (in target 'React-Core-AccessibilityResources' from project 'Pods')

Any ideas about that?

[Jin-seop]

xcode downgrade 13.4.1 version.

[christianrank]

Downgrade is not a real solution, only a quick fix.

[christianrank]

I found out this script actually works on my CI, just this doesn't.

[ansarikhurshid786]

i simply select provision profile and without clear build i can archive project it works for me.

[kelset]

can you folks try this workaround? expo/expo@d970a9e

it's the one the Expo team has been implementing and it seems to be in line with some comments in the pods issue.

[hamidhadi]

@kelset That workaround works for me.

[tomwanzek]

For current reference, we just ran into this issue when trying to upgrade our CI/CD pipeline to use

• Fastlane 2.212.1
• XCode 14.2

Incidentally, what seems to have made a difference is upgrading Cocoapods to 1.12.0. To be clear we did not add any of the workarounds in the Pod file post_install hooks as described earlier.

[liamjones]

Incidentally, what seems to have made a difference is upgrading Cocoapods to 1.12.0. To be clear we did not add any of the workarounds in the Pod file post_install hooks as described earlier.

Yes, Cocoapods 1.12.0 contains a fix for this issue (although it was missing from the release notes): CocoaPods/CocoaPods@141a082

[penghuiliada]

For current reference, we just ran into this issue when trying to upgrade our CI/CD pipeline to use

• Fastlane 2.212.1
• XCode 14.2

Incidentally, what seems to have made a difference is upgrading Cocoapods to 1.12.0. To be clear we did not add any of the workarounds in the Pod file post_install hooks as described earlier.

Hi @tomwanzek , the cocoapods upgrade also helped us, now we can publish our app to TestFlight, but apple still complains that ITMS-90129: The bundle uses a bundle name or display name that is already taken., we didn't change any name for our app.

before upgrading cocoapods, we can't even publish to TestFlight, the publish step already failed with that error message.

do you have any idea?
Thanks! 🙏

[Harukisatoh]

For some reason upgrading cocoapods to 1.12.0 works locally, but doesn't work for AppCenter which is the CI I'm currently using. The post_install workaround also appears to not work for me.

[Harukisatoh]

For some reason upgrading cocoapods to 1.12.0 works locally, but doesn't work for AppCenter which is the CI I'm currently using. The post_install workaround also appears to not work for me.

For those who has the same issue as me:

Here's a link that explains the post install workaround: https://stackoverflow.com/a/39949186
After every pod install execution, the post install script is executed too. This script is used to disable the code signing on each pod library.

My problem was that this script was never being executed on CI. After a lot of hours trying to figure out why, I've finally found the cause in this link: https://learn.microsoft.com/en-us/appcenter/build/ios/#38-cocoapods
In the warning section they say: "If the repository already contains a /Pods folder, App Center assumes you've checked in the pods in your repository and will no longer perform pod install". And luckily (or no) in my repo I had the /Pods folder commited, and because of that, App Center never executed the script.

After that, the only thing I had to do was to execute a pod install locally, and commit all changes from /Pods folder to the repo, this way App Center received the already signed pods.

[tomwanzek]

@penghuiliada Unfortunately, I have not much to add about

TMS-90129: The bundle uses a bundle name or display name that is already taken.

It's an issue we have not encountered (so far 🤞). As you suggested with the "before upgrading cocoapods ", this seems to have been a preexisting issue and not a new one introduced with Cocoapods 1.12.0. Good luck, hope you find a solution.

[penghuiliada]

thank you @tomwanzek for checking!

Sorry, forgot to give update here, yes, it's indeed something wrong with our app, i documented the problem and solution here: CocoaPods/CocoaPods#11402 (comment)

In case someone has the same problem.

[kennedy-f]

Today, I encountered a similar issue and after inspecting the Expo code, I found a solution in their GitHub repository: https://github.com/expo/expo/blob/main/ios/Podfile#L78

To resolve my issue, I added the code snippet above to my Podfile, ran pod install again, and was able to successfully archive my application and distribute.

    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
    
    installer.target_installation_results.pod_target_installation_results
         .each do |pod_name, target_installation_result|
      target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
        resource_bundle_target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end
  end

[sanoofrahiman960]

post_install do |installer|
react_native_post_install(installer)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end

1, when run i code " npx react-native run-ios"
i got error like this how to solve i stuck with 2 weeks
"
** BUILD FAILED **

The following build commands failed:
CompileC /Users/sanoofrahimanj/Library/Developer/Xcode/DerivedData/milmaDataEntry-awvvzufrdwnctpalvkdkgvyaxbpw/Build/Intermediates.noindex/milmaDataEntry.build/Debug-iphonesimulator/milmaDataEntry.build/Objects-normal/arm64/AppDelegate.o /Users/sanoofrahimanj/Desktop/Workspace/DonamsTechLabs/milma-pms-app/ios/milmaDataEntry/AppDelegate.mm normal arm64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'milmaDataEntry' from project 'milmaDataEntry')
(1 failure)"

my pod file attached below

my system info run :-npx react native info
System:
OS: macOS 12.5
CPU: (8) arm64 Apple M1
Memory: 107.86 MB / 8.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.17.1 - ~/.nvm/versions/node/v16.17.1/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.4.1 - ~/.nvm/versions/node/v16.17.1/bin/npm
Watchman: 2023.02.27.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /Users/sanoofrahimanj/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 19.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.1.0 => 18.2.0
react-native: ^0.70.6 => 0.70.12
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

[thellecodes]

Today, I encountered a similar issue and after inspecting the Expo code, I found a solution in their GitHub repository: https://github.com/expo/expo/blob/main/ios/Podfile#L78

To resolve my issue, I added the code snippet above to my Podfile, ran pod install again, and was able to successfully archive my application and distribute.

    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
    
    installer.target_installation_results.pod_target_installation_results
         .each do |pod_name, target_installation_result|
      target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
        resource_bundle_target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end
  end

Worked for me 😇