Skip to content

fix: Forward device option in UI critical test lanes - #8709

Merged
itaybre merged 2 commits into
mainfrom
fix/ui-critical-tests-device-passthrough
Aug 7, 2026
Merged

fix: Forward device option in UI critical test lanes#8709
itaybre merged 2 commits into
mainfrom
fix/ui-critical-tests-device-passthrough

Conversation

@itaybre

@itaybre itaybre commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Description

The ui_critical_tests_ios_swiftui_envelope and ui_critical_tests_ios_swiftui_all Fastlane lanes were missing the |options| block parameter and weren't forwarding device: options[:device] to run_ui_tests.

The CI workflow (ui-tests-common.yml) passes device:"iPhone 16 Pro (18.5)" on the command line, but these two lanes silently ignored it. Fastlane then fell back to picking whatever simulator it found first — iPhone 14 Pro on iOS 16.4. Running UI tests on iOS 16.4 with Xcode 16.4 triggers the known "Test runner never began executing tests after launching" XCTest connection issue intermittently.

Every other UI test lane (ui_tests_ios_swiftui, ui_tests_ios_swift6, ui_tests_ios_objc, ui_tests_ios_swift) correctly accepts and forwards options[:device] — these two were the only ones missing it.

How to verify

The "Test iOS 18 V4 / UI Tests Common" job in the Test UI Critical workflow should now consistently target the correct iOS 18.5 simulator instead of falling back to iOS 16.4.

#skip-changelog

Closes #8711

The ui_critical_tests_ios_swiftui_envelope and
ui_critical_tests_ios_swiftui_all lanes were missing the
options block parameter, silently ignoring the device
passed by CI. This caused Fastlane to pick an arbitrary
simulator (iPhone 14 Pro on iOS 16.4) instead of the
intended target (iPhone 16 Pro on iOS 18.5), leading to
flaky "Test runner never began executing tests" failures.
@itaybre itaybre added the run-full-ci Allows gated GitHub Action workflows to run for a labelled pull request label Aug 6, 2026
@itaybre
itaybre marked this pull request as ready for review August 6, 2026 15:06
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 1232.85 ms 1265.65 ms 32.80 ms
Size 24.14 KiB 1.27 MiB 1.25 MiB

Baseline results on branch: main

Startup times

Revision Plain With Sentry Diff
59213ba 1223.66 ms 1258.02 ms 34.36 ms
23b642a 1235.62 ms 1270.53 ms 34.92 ms
70e2dea 1219.63 ms 1251.72 ms 32.09 ms
9c0db16 1219.04 ms 1247.83 ms 28.78 ms
4da7fcb 1209.38 ms 1251.78 ms 42.40 ms
a250b4d 1217.19 ms 1250.80 ms 33.62 ms
75d7de0 1217.24 ms 1251.27 ms 34.03 ms
49cc12d 1227.33 ms 1263.21 ms 35.89 ms
00009c7 1231.69 ms 1265.73 ms 34.04 ms
c1c9578 1219.32 ms 1261.74 ms 42.43 ms

App size

Revision Plain With Sentry Diff
59213ba 24.14 KiB 1.22 MiB 1.20 MiB
23b642a 24.14 KiB 1.24 MiB 1.22 MiB
70e2dea 24.14 KiB 1.18 MiB 1.15 MiB
9c0db16 24.14 KiB 1.19 MiB 1.17 MiB
4da7fcb 24.14 KiB 1.18 MiB 1.16 MiB
a250b4d 24.14 KiB 1.22 MiB 1.20 MiB
75d7de0 24.14 KiB 1.24 MiB 1.22 MiB
49cc12d 24.14 KiB 1.16 MiB 1.13 MiB
00009c7 24.14 KiB 1.24 MiB 1.21 MiB
c1c9578 24.14 KiB 1.20 MiB 1.18 MiB

Previous results on branch: fix/ui-critical-tests-device-passthrough

Startup times

Revision Plain With Sentry Diff
ae493e0 1221.96 ms 1257.13 ms 35.18 ms

App size

Revision Plain With Sentry Diff
ae493e0 24.14 KiB 1.27 MiB 1.25 MiB

@itaybre
itaybre enabled auto-merge (squash) August 6, 2026 15:48
@itaybre
itaybre merged commit ed3c8b8 into main Aug 7, 2026
223 checks passed
@itaybre
itaybre deleted the fix/ui-critical-tests-device-passthrough branch August 7, 2026 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved run-full-ci Allows gated GitHub Action workflows to run for a labelled pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: Forward device option in UI critical test lanes

2 participants