Skip to content

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

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

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

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

native-tests.yml

on: pull_request
Ready-to-merge gate  /  Missing "ready-to-merge" label
3s
Ready-to-merge gate / Missing "ready-to-merge" label
diff_check  /  diff_check
10s
diff_check / diff_check
detect-changes  /  Detect file changes
5s
detect-changes / Detect file changes
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 1 warning, and 1 notice
ios
The run was canceled by @github-actions[bot].
Native Tests
The run was canceled by @github-actions[bot].
ios
The operation was canceled.
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/
Resource Utilization
Peak CPU utilization: 4.00 cores (100.00% of 4.00) at 53s Peak memory utilization: 9.6 GB (55.72% of 17 GB) at 150s