Skip to content

fix: resolve race condition in location listener causing NullPointerE… #130

fix: resolve race condition in location listener causing NullPointerE…

fix: resolve race condition in location listener causing NullPointerE… #130

Triggered via push April 21, 2026 09:26
Status Success
Total duration 1m 42s
Artifacts
build-and-test  /  lint
26s
build-and-test / lint
build-and-test  /  check-objc-formatting
11s
build-and-test / check-objc-formatting
build-and-test  /  check-java-and-kotlin-formatting
14s
build-and-test / check-java-and-kotlin-formatting
build-and-test  /  test
2s
build-and-test / test
build-and-test  /  build-library
25s
build-and-test / build-library
build-and-test  /  build-android
17s
build-and-test / build-android
build-and-test  /  build-ios
1m 11s
build-and-test / build-ios
release-please
22s
release-please
publish  /  ...  /  build-android
publish / build-and-test / build-android
publish  /  ...  /  build-ios
publish / build-and-test / build-ios
publish  /  ...  /  build-library
publish / build-and-test / build-library
publish  /  ...  /  check-java-and-kotlin-formatting
publish / build-and-test / check-java-and-kotlin-formatting
publish  /  ...  /  check-objc-formatting
publish / build-and-test / check-objc-formatting
publish  /  ...  /  lint
publish / build-and-test / lint
publish  /  ...  /  test
publish / build-and-test / test
publish  /  publish
publish / publish
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
build-and-test / 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. 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/
build-and-test / 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. 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/
build-and-test / 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-node@v3. 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/
build-and-test / 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. 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/
build-and-test / 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. 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/
build-and-test / 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. 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/
build-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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-and-test / 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]
release-please
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: googleapis/release-please-action@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/