Repository navigation
Correct route and dynamic param extraction for Expo Router (#6157) #13943
alwxsample-application.yml
on: pull_request
Ready-to-merge gate
/
Missing "ready-to-merge" label
2s
diff_check
/
diff_check
12s
detect-changes
/
Detect file changes
5s
Matrix: build-android
Matrix: build-ios
Matrix: build-macos
Test android production REV2
Test ios production REV2
0s
Annotations
13 errors, 9 warnings, and 4 notices
|
Build new ios dev no-frameworks
The run was canceled by @github-actions[bot].
|
|
Build new ios dev no-frameworks
The operation was canceled.
|
|
Build new android dev
The run was canceled by @github-actions[bot].
|
|
Build new android dev
The operation was canceled.
|
|
Build new android production
The run was canceled by @github-actions[bot].
|
|
Build new android production
The operation was canceled.
|
|
Build legacy macos production
The run was canceled by @github-actions[bot].
|
|
Build legacy macos production
The operation was canceled.
|
|
Build legacy macos dev
The run was canceled by @github-actions[bot].
|
|
Build legacy macos dev
The operation was canceled.
|
|
Build new ios production no-frameworks
The run was canceled by @github-actions[bot].
|
|
Build new ios production no-frameworks
The operation was canceled.
|
|
Sample Application
The run was canceled by @github-actions[bot].
|
|
Build new ios dev no-frameworks
No files were found with the provided path: samples/react-native/ios/*.log. No artifacts will be uploaded.
|
|
Build new android dev
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/actions/setup-gradle@v3.5.0. 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 new android dev
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
Build new android dev
No files were found with the provided path: samples/react-native/android/*.log. No artifacts will be uploaded.
|
|
Build new android dev
Failed to restore gradle-home-v1|Linux|build-android[76945e00d18b094858850ca2f6755e43]-dc28ceaf35517e3ff839c8a5c983f988ea14ef79: Error: Cache service responded with 400
|
|
Build new android production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/actions/setup-gradle@v3.5.0. 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 new android production
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
Build new android production
No files were found with the provided path: samples/react-native/android/*.log. No artifacts will be uploaded.
|
|
Build new android production
Failed to restore gradle-home-v1|Linux|build-android[26c3db2f35373b3d09e85a212763dd50]-dc28ceaf35517e3ff839c8a5c983f988ea14ef79: Error: Cache service responded with 400
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 49s
Peak memory utilization: 9.6 GB (55.85% of 17 GB) at 30s
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 54s
Peak memory utilization: 10 GB (58.01% of 17 GB) at 42s
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 59s
Peak memory utilization: 9.9 GB (57.46% of 17 GB) at 49s
|
|
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 60s
Peak memory utilization: 9.6 GB (56.00% of 17 GB) at 53s
|