Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c1e323688fd81a25caa38c78aa6df2d33d3e20d9. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/3F15E1YASVSDG/ObjectiveC-1172D6382X38X.pcm: No such file or directory

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/3F15E1YASVSDG/Foundation-1K45JSBD9P9SO.pcm: No such file or directory

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/9SPKHPNF0S77/Foundation-1K45JSBD9P9SO.pcm: No such file or directory

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/9SPKHPNF0S77/React-1B72Z8D7V0QFL.pcm: No such file or directory

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/9SPKHPNF0S77/UIKit-4378JDRC8MEN.pcm: No such file or directory

The value for NSLocationWhenInUseUsageDescription must be a non-empty string. (in target 'testing' from project 'testing')

ld: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.7003.10.jXtImu/Metal.xctoolchain/usr/lib/swift/iphonesimulator' not found

ld: ignoring duplicate libraries: '-lc++'

variable 'args' was never mutated; consider changing to 'let' constant

Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

The following taps are not trusted: aws/tap azure/bicep wix/brew Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep wix/brew Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep wix/brew To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.

The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c1e323688fd81a25caa38c78aa6df2d33d3e20d9. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/1X1NBCYP2L7ED/React-26REBFJTMKJCY.pcm: No such file or directory

/Users/runner/work/react-native-firebase/react-native-firebase/tests/ios/build/ModuleCache.noindex/1X1NBCYP2L7ED/UIKit-4378JDRC8MEN.pcm: No such file or directory

The value for NSLocationWhenInUseUsageDescription must be a non-empty string. (in target 'testing' from project 'testing')

ld: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.7003.10.kD5XTu/Metal.xctoolchain/usr/lib/swift/iphonesimulator' not found

ld: ignoring duplicate libraries: '-lc++'

ld: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.7003.10.kD5XTu/Metal.xctoolchain/usr/lib/swift/iphonesimulator' not found

ld: ignoring duplicate libraries: '-lc++'

variable 'args' was never mutated; consider changing to 'let' constant

variable 'args' was never mutated; consider changing to 'let' constant

Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

The following taps are not trusted: aws/tap azure/bicep wix/brew Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep wix/brew Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep wix/brew To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.