Skip to content

fix: qr scanner appearing before the confirmations screen cp-7.77.0 (… #1361

fix: qr scanner appearing before the confirmations screen cp-7.77.0 (…

fix: qr scanner appearing before the confirmations screen cp-7.77.0 (… #1361

Triggered via push May 14, 2026 15:09
Status Failure
Total duration 40m 18s
Artifacts 5
Expo dev build (main-dev-expo)  /  ...  /  generate-build-version
Expo dev build (main-dev-expo) / update-build-version / generate-build-version / generate-build-version
Expo dev build (main-dev-expo)  /  ...  /  bump-version
Expo dev build (main-dev-expo) / update-build-version / bump-version
Expo dev build (main-dev-expo)  /  prepare
2m 32s
Expo dev build (main-dev-expo) / prepare
Matrix: Expo dev build (main-dev-expo) / setup-dependencies
Matrix: Expo dev build (main-dev-expo) / build
Expo dev build (main-dev-expo)  /  Emit build metadata
0s
Expo dev build (main-dev-expo) / Emit build metadata
Fit to window
Zoom out
Zoom in

Annotations

1 error, 7 warnings, and 4 notices
Expo dev build (main-dev-expo) / build (ios)
Final attempt failed. Child_process exited with error code 1
Expo dev build (main-dev-expo) / prepare
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-node@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/
Expo dev build (main-dev-expo) / Setup Dependencies (android) / Setup Node Modules (android)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
Expo dev build (main-dev-expo) / Setup Dependencies (ios) / Setup Node Modules (ios)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@44511735964dcb71245e7e55f72539531f7bc0eb. 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/
Expo dev build (main-dev-expo) / build (android)
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/setup-java@v4, actions/setup-node@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4, cirruslabs/cache@bba69c6578b863ad0398ad40567bd2ef70290fe0, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
Expo dev build (main-dev-expo) / build (ios)
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/setup-node@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@44511735964dcb71245e7e55f72539531f7bc0eb. 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/
Expo dev build (main-dev-expo) / build (ios)
Attempt 2 failed. Reason: Child_process exited with error code 1
Expo dev build (main-dev-expo) / build (ios)
Attempt 1 failed. Reason: Timeout of 600000ms hit
Resource Utilization
Peak CPU utilization: 12.11 cores (75.71% of 16.00) at 46s Peak memory utilization: 4.4 GB (8.64% of 50 GB) at 60s
Resource Utilization
Peak CPU utilization: 8.00 cores (100.00% of 8.00) at 1s Peak memory utilization: 10 GB (30.51% of 34 GB) at 210s
Omni Cache
Cache hits: 1 Cache misses: 0 Hit rate: 100.0% Downloads: count=1 total=4.1 GiB avg=4.1 GiB avgTime=1m7.073s avgSpeed=66 MB/s Uploads: none::notice title=Resource Utilization::Peak CPU utilization: 16.00 cores (99.98% of 16.00) at 570s Peak memory utilization: 11 GB (22.17% of 50 GB) at 600s
Resource Utilization
Peak CPU utilization: 4.40 cores (55.04% of 8.00) at 630s Peak memory utilization: 12 GB (34.59% of 34 GB) at 670s

Artifacts

Produced during runtime
Name Size Digest
android-apk-main-dev-expo
142 MB
sha256:9b794685ca956e9339fea898ddf5e7ae99bf28da481cc8c90e16053b58078c5f
android-test-apk-main-dev-expo
3.69 MB
sha256:6e5f2db5c1eba5bfe0608b7fd6b2b7a98d1bed9365d46abca20ca1aa0b70918d
build-env-main-dev-expo-android
601 Bytes
sha256:117bdb0c27017ae18678424f46fe566c3eb74d19c62f2ab324a7c1427185d078
node-modules-main-dev-expo-android Expired
635 MB
sha256:4b074b7b594c167f6829f4f8bc944311a90480b750d7294f7eaa43608f428f19
node-modules-main-dev-expo-ios Expired
631 MB
sha256:ee849987269070adf23d5764d4f5f40bfd5b27bfee44f4126c765228b3c758ff