Skip to content

Build iOS Dual Versions and Upload to BrowserStack #7

Build iOS Dual Versions and Upload to BrowserStack

Build iOS Dual Versions and Upload to BrowserStack #7

Status Failure
Total duration 11m 56s
Artifacts 2

build-ios-upload-to-browserstack.yml

on: workflow_dispatch
Check if iOS builds are needed
3s
Check if iOS builds are needed
Trigger iOS with-SRP Build  /  ...  /  generate-build-version
Trigger iOS with-SRP Build / update-build-version / generate-build-version / generate-build-version
Trigger iOS without-SRP Build  /  ...  /  generate-build-version
Trigger iOS without-SRP Build / update-build-version / generate-build-version / generate-build-version
Trigger iOS with-SRP Build  /  ...  /  bump-version
Trigger iOS with-SRP Build / update-build-version / bump-version
Trigger iOS without-SRP Build  /  ...  /  bump-version
Trigger iOS without-SRP Build / update-build-version / bump-version
Trigger iOS with-SRP Build  /  prepare
1m 17s
Trigger iOS with-SRP Build / prepare
Trigger iOS without-SRP Build  /  prepare
1m 31s
Trigger iOS without-SRP Build / prepare
Matrix: Trigger iOS with-SRP Build / setup-dependencies
Matrix: Trigger iOS without-SRP Build / setup-dependencies
Matrix: Trigger iOS with-SRP Build / build
Matrix: Trigger iOS without-SRP Build / build
Trigger iOS with-SRP Build  /  Emit build metadata
0s
Trigger iOS with-SRP Build / Emit build metadata
Trigger iOS without-SRP Build  /  Emit build metadata
0s
Trigger iOS without-SRP Build / Emit build metadata
Download IPAs and Upload to BrowserStack
0s
Download IPAs and Upload to BrowserStack
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 3 warnings, and 2 notices
Trigger iOS with-SRP Build / build (ios)
Input required and not supplied: path
Trigger iOS without-SRP Build / build (ios)
Input required and not supplied: path
Trigger iOS with-SRP Build / 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, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@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/
Resource Utilization
Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.
Trigger iOS without-SRP Build / 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, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@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/
Resource Utilization
Peak CPU utilization: 3.30 cores (41.19% of 8.00) at 46s Peak memory utilization: 11 GB (31.71% of 34 GB) at 190s
Resource Utilization
Peak CPU utilization: 5.12 cores (63.96% of 8.00) at 52s Peak memory utilization: 12 GB (34.23% of 34 GB) at 260s