feat: upgrade ios nav sdk to 10.10.0 and android to 7.4.0 #590
illuminati1911ci.yml
on: pull_request
lint
1m 39s
check-objc-formatting
49s
check-java-and-kotlin-formatting
15s
test
3s
build-library
1m 46s
build-android
9m 57s
build-ios
8m 32s
Annotations
6 errors and 16 warnings
|
build-ios
Process completed with exit code 1.
|
|
build-ios:
clang++#L0
linker command failed with exit code 1 (use -v to see invocation)
|
|
build-ios
ld: symbol(s) not found for architecture x86_64
|
|
build-ios
"_OBJC_CLASS_$_UIGlassEffect", referenced from:
|
|
build-ios
Undefined symbols for architecture x86_64
|
|
build-ios
react-native-navigation-sdk-sample#build:ios: command (/Users/runner/work/react-native-navigation-sdk/react-native-navigation-sdk/example) /private/var/folders/t5/f77_gwnj6p95qxy9py3fckx00000gn/T/xfs-00b5eb04/yarn run build:ios exited (1)
|
|
check-java-and-kotlin-formatting
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/setup-java@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
check-objc-formatting
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. 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/
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-library
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-ios
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L164
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'ScopeDepth' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/Public/DebuggerTypes.h#L78
implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'uint32_t' (aka 'unsigned int') [-Wshorten-64-to-32]
|
|
build-ios:
example/ios/Pods/Headers/Public/hermes-engine/hermes/inspector/chrome/CDPHandler.h#L107
parameter 'onDisconnect' not found in the function declaration [-Wdocumentation]
|
|
build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
build-ios:
example/node_modules/react-native/ReactCommon/reactperflogger/fusebox/FuseboxTracer.h#L26
declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
|
|
build-android
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, actions/setup-java@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|