"Multiple commands produce" error on AccessibilityResources.bundle after upgrading to 0.63.2

[sgup]

Environment

System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 964.21 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    Yarn: 1.22.4 - ~/.nvm/versions/node/v12.18.3/bin/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

Upgrading version

0.63.2

Description

iOS Archive step fails on Generic iPhone Device.

Showing All Messages
Multiple commands produce '/Users/username/Library/Developer/Xcode/DerivedData/AppName-cpjutrymlhydfneedaklsmdyabol/Build/Intermediates.noindex/ArchiveIntermediates/AppName/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AccessibilityResources.bundle':

1) Target 'React-Core.common-AccessibilityResources' has create directory command with output '/Users/username/Library/Developer/Xcode/DerivedData/AppName-cpjutrymlhydfneedaklsmdyabol/Build/Intermediates.noindex/ArchiveIntermediates/AppName/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AccessibilityResources.bundle'

2) Target 'React-Core.common-CoreModulesHeaders-AccessibilityResources' has create directory command with output '/Users/username/Library/Developer/Xcode/DerivedData/AppName-cpjutrymlhydfneedaklsmdyabol/Build/Intermediates.noindex/ArchiveIntermediates/AppName/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AccessibilityResources.bundle'

[AtharZaib]

Still exists . Can't make release build. HELP !!!

[Domiciano]

I got the same issue

[tp26610]

The solution https://github.com/facebook/react-native/issues/29709#issuecomment-695180617 solve the issue for me

[saif482]

i am still facing the same since 3 days

[kobykruz]

Any solutions?

[harshitsmt]

Any solutions?

[ghills]

I am also having this issue after upgrading from 0.61.5 to 0.63.3.

[cedced19]

Do you have the same issue or an issue like mine : https://github.com/facebook/react-native/issues/30335

[ghills]

@cedced19 my issue was slightly different but it was with the same AccessibilityResources.bundle. First I was getting a signing error on AppCenter that a Team ID needed to be set on that bundle to do signing. I tried applying the podfile workaround from https://github.com/facebook/react-native/issues/29709#issue-682603693 but then I was getting an error about failures to copy that bundle (presumably because it wasn't being built).

I was able to fix my project such that I don't require that workaround. What I had to do was open the scheme editor in Xcode. My project had 2 targets - the main app being built and the Podfile project. I removed the Podfile project from the scheme build targets and I stopped having trouble with AccessibilityResources.bundle.

Caveat being I'm not exactly sure why that was the solution other than potentially duplicate build targets (because the app is dependent on the Pods project already) but I was just going through the RnDiffApp for 0.63.3 and comparing iOS settings to my project to try to find differences.

[crisecheverria]

Tried the same with AppCenter, didn't work!

[chgsilva]

same error

[crisecheverria]

@cedced19 my issue was slightly different but it was with the same AccessibilityResources.bundle. First I was getting a signing error on AppCenter that a Team ID needed to be set on that bundle to do signing. I tried applying the podfile workaround from facebook/react-native#29709 (comment) but then I was getting an error about failures to copy that bundle (presumably because it wasn't being built).

I was able to fix my project such that I don't require that workaround. What I had to do was open the scheme editor in Xcode. My project had 2 targets - the main app being built and the Podfile project. I removed the Podfile project from the scheme build targets and I stopped having trouble with AccessibilityResources.bundle.

Caveat being I'm not exactly sure why that was the solution other than potentially duplicate build targets (because the app is dependent on the Pods project already) but I was just going through the RnDiffApp for 0.63.3 and comparing iOS settings to my project to try to find differences.

How did you remove the Podfile project from the Scheme? I want to be able to build with App Center as well but isn't possible using all the tricks.

[ghills]

@cedced19 my issue was slightly different but it was with the same AccessibilityResources.bundle. First I was getting a signing error on AppCenter that a Team ID needed to be set on that bundle to do signing. I tried applying the podfile workaround from facebook/react-native#29709 (comment) but then I was getting an error about failures to copy that bundle (presumably because it wasn't being built). I was able to fix my project such that I don't require that workaround. What I had to do was open the scheme editor in Xcode. My project had 2 targets - the main app being built and the Podfile project. I removed the Podfile project from the scheme build targets and I stopped having trouble with AccessibilityResources.bundle. Caveat being I'm not exactly sure why that was the solution other than potentially duplicate build targets (because the app is dependent on the Pods project already) but I was just going through the RnDiffApp for 0.63.3 and comparing iOS settings to my project to try to find differences.

How did you remove the Podfile project from the Scheme? I want to be able to build with App Center as well but isn't possible using all the tricks.

Going from memory here so it may not be exact -

• Scheme menu -> manage schemes
• Select the scheme being used on AppCenter
• Make sure you are on the build tab (should be the first one)
• In the build targets I had both the app and Podfile listed separately. I removed the Podfile from this screen.

[Benjyben]

In my case, I had this problem when I wanted to archive my application but i resolved adding in Podfile this line inside post_install and installer.pods_project.target.each do |target| :

if target.name == "React-Core.common-AccessibilityResources" target.remove_from_project end

[CHNB128]

Same issue after upgrading to 0.64.0

[CHNB128]

Thanks a lot, @Benjyben, this solved this issue for me. Waiting for official path.

[selimsevencan]

react-native => 0.66.0

In my part, I added to every target use_react_native! and it worked. Maybe it helps.

[Benjyben]

react-native => 0.66.0 In my part, I added to every target use_react_native!

I will try thanks !

[mdrajibsk8]

anyone find any solution. I tried every possible way but nothing working.

[mdrajibsk8]

This works for me. After moving the react-native-permissions inside use_react_native. It's working for me. Here is my Podfile -

[markosrx]

Any solutions?

[thanhluantl2304]

react-native => 0.66.0

In my part, I added to every target use_react_native! and it worked. Maybe it helps.

i confirm this is the right answer

[ryolay]

Still having the issue