fatal error: module 'RCTDeprecation' in AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/ios/build/ModuleCache.noindex/2NDNS140IEAAU/RCTDeprecation-4BALPFJM82B5.pcm' (imported by AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/ios/build/Build/Intermediates.noindex/PrecompiledHeaders/ReactTestApp-Bridging-Header-swift_2QR0MG5TVFPQB-clang_2NDNS140IEAAU.pch') is not defined in any loaded module map file; maybe you need to load '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/node_modules/.generated/ios/../../../ios/Pods/Headers/Public/RCTDeprecation/RCTDeprecation.modulemap'?

fatal error: module 'RCTDeprecation' in AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/ios/build/ModuleCache.noindex/WHHJGSLDO6BJ/RCTDeprecation-4BALPFJM82B5.pcm' (imported by AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/ios/build/Build/Intermediates.noindex/PrecompiledHeaders/ReactTestApp-Bridging-Header-swift_32X15ZCLESI52-clang_WHHJGSLDO6BJ.pch') is not defined in any loaded module map file; maybe you need to load '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/node_modules/.generated/ios/../../../ios/Pods/Headers/Public/RCTDeprecation/RCTDeprecation.modulemap'?

fatal error: module 'RCTDeprecation' in AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/macos/build/ModuleCache.noindex/1919ZBLV2ZW3Q/RCTDeprecation-12GD0PQUUFD5V.pcm' (imported by AST file '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/macos/build/Build/Intermediates.noindex/PrecompiledHeaders/ReactTestApp-Bridging-Header-swift_3S0VGAYIO1YQV-clang_1919ZBLV2ZW3Q.pch') is not defined in any loaded module map file; maybe you need to load '/Users/runner/work/fluentui-react-native/fluentui-react-native/apps/fluent-tester/node_modules/.generated/macos/../../../macos/Pods/Headers/Public/RCTDeprecation/RCTDeprecation.modulemap'?

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

forming 'UnsafeRawPointer' to an inout variable of type String exposes the internal representation rather than the string contents.

forming 'UnsafeRawPointer' to an inout variable of type String exposes the internal representation rather than the string contents.

forming 'UnsafeRawPointer' to an inout variable of type String exposes the internal representation rather than the string contents.

forming 'UnsafeRawPointer' to an inout variable of type String exposes the internal representation rather than the string contents.

extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode

extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode

extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode

extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode

ONLY_ACTIVE_ARCH=YES requested with multiple ARCHS and no active architecture could be computed; building for all applicable architectures (in target 'MicrosoftFluentUI-FluentUIResources-ios' from project 'Pods')

'init(contentsOf:)' was deprecated in macOS 15: Use `init(contentsOf:encoding:)` instead

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.6, but the range of supported deployment target versions is 10.13 to 15.5.99. (in target 'RCTDeprecation' from project 'Pods')

Run script build phase '[CP-User] [RN]Check rncore' 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 'React-Fabric' from project 'Pods')