Skip to content

feat: Add network details for session replay on iOS #13313

feat: Add network details for session replay on iOS

feat: Add network details for session replay on iOS #13313

Triggered via pull request March 25, 2026 01:23
Status Success
Total duration 1h 6m 2s
Artifacts 9

build.yml

on: pull_request
Matrix: build-sentry-native
test-solution-filters
43s
test-solution-filters
Matrix: build-sentry
Matrix: unsupported-aot
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 21 warnings
.NET (linux-x64)
You may need to build the project on another operating system or architecture, or update the .NET SDK.
.NET (linux-x64)
The project depends on the following workload packs that do not exist in any of the workloads available in this installation: Microsoft.iOS.Sdk.net9.0_26.0
Trim analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
Trim analysis
Already linked: /opt/homebrew/Cellar/mono/6.14.1
.NET (linux-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
MSBuild
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f, microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
MSBuild
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
.NET (linux-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
.NET (win-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
.NET (macos)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
.NET (macos)
Already linked: /opt/homebrew/Cellar/mono/6.14.1
.NET (win-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
Unsupported AOT (linux-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/
Unsupported AOT (win-x86)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, android-actions/setup-android@07976c6290703d34c16d382cb36445f98bb43b1f. 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/

Artifacts

Produced during runtime
Name Size Digest
032358e6b631d21cac6579f57ed95ffa3e48cba8
165 MB
sha256:9f70707eb48d7777a3fab39b95a0df6fad9ccb617458a8bbdbdbbf1ccf18e389
Windows-msbuild-logs
95.8 MB
sha256:4591cfdde00778bfedb873bb9ce2ee47cdc43bdb0954ac57ea51d5438aa8fc84
linux-arm64-build-logs
50.4 MB
sha256:30f8df69fc74d501a458830c7ad73380ca781d0afd5fd34a74673398ddcc06b8
linux-musl-arm64-build-logs
50.2 MB
sha256:299a3fbd9244009a8574e54e2280f8c4f70066eeec10113f30457a66165cbd01
linux-musl-x64-build-logs
50.2 MB
sha256:789a929fe333b5fe5e58e0804877022c4560cd9851c44b212e2b2929ef811637
linux-x64-build-logs
83.2 MB
sha256:471f35515239e1486efd1da618a6f0f637b4f9729568e15b79a5b7b7ad8dc633
macos-build-logs
117 MB
sha256:e770f7d872a91c3e300f257e2261fd211758401b72db28340b0c2a55237d4f7d
win-arm64-build-logs
73.1 MB
sha256:9516d6f088825211afa318668c5371e0686004c2c535717835ec2e4549f4c0ed
win-x64-build-logs
77.4 MB
sha256:2a558479906a7a27d255a876e8c785297a57811afde251192c6405de3523ace0