Skip to content

fix(ios): Guard replay postInit behind runtime session replay check #7377

fix(ios): Guard replay postInit behind runtime session replay check

fix(ios): Guard replay postInit behind runtime session replay check #7377

Triggered via pull request March 23, 2026 12:35
Status Cancelled
Total duration 3m 55s
Artifacts 2

sample-application-expo.yml

on: pull_request
Ready-to-merge gate  /  Missing "ready-to-merge" label
4s
Ready-to-merge gate / Missing "ready-to-merge" label
diff_check  /  diff_check
8s
diff_check / diff_check
detect-changes  /  Detect file changes
7s
detect-changes / Detect file changes
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 7 warnings, and 2 notices
Build ios dev no-frameworks
The run was canceled by @github-actions[bot].
Build ios production no-frameworks
The run was canceled by @github-actions[bot].
Build ios dev dynamic-frameworks
The run was canceled by @github-actions[bot].
Build ios dev dynamic-frameworks
The operation was canceled.
Build ios production dynamic-frameworks
The run was canceled by @github-actions[bot].
Build ios production dynamic-frameworks
The operation was canceled.
Sample Application Expo
The run was canceled by @github-actions[bot].
detect-changes / Detect file changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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 dev dynamic-frameworks
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 ios dev dynamic-frameworks
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build ios dev dynamic-frameworks
Failed to restore gradle-home-v1|macOS|build[385f91061950098928b58857312de725]-7eb78ac15e9c64d0184722bd03b29d9249d318e6: Error: Cache service responded with 400
Build ios production dynamic-frameworks
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 ios production dynamic-frameworks
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build ios production dynamic-frameworks
Failed to restore gradle-home-v1|macOS|build[a8052957b43991b26010494632b0a942]-7eb78ac15e9c64d0184722bd03b29d9249d318e6: Error: Cache service responded with 400
Resource Utilization
Peak CPU utilization: 3.64 cores (90.92% of 4.00) at 80s Peak memory utilization: 9.1 GB (52.93% of 17 GB) at 200s
Resource Utilization
Peak CPU utilization: 3.91 cores (97.67% of 4.00) at 200s Peak memory utilization: 9.4 GB (54.46% of 17 GB) at 200s

Artifacts

Produced during runtime
Name Size Digest
build-sample-expo-ios-dev-dynamic-frameworks-logs
112 KB
sha256:4b3018f72cdb16c58e20cb7457f0b288dc7dc6a88627eeef7d23856cd1cd01ab
build-sample-expo-ios-production-dynamic-frameworks-logs
60.6 KB
sha256:532f4b67a4d3be7b1c5727ba42b978c24d3cf73647acd47385b59ae6356e72fb