Run 32148: the UI probe fails with an apparently empty accessibility tree — the app reaches Running Foreground but openAboutBtn (green in run 32029) never materialises. Automation permission is granted on the VM but the hierarchy still appears empty.
XCTest already captures the a11y hierarchy snapshot + screenshots into the xcresult on failure, but the workflow doesn't upload it. Add an if: failure() step uploading build/DerivedData-test/Logs/Test as an artifact so failures can be triaged without runner access.
Run 32148: the UI probe fails with an apparently empty accessibility tree — the app reaches Running Foreground but `openAboutBtn` (green in run 32029) never materialises. Automation permission is granted on the VM but the hierarchy still appears empty.
XCTest already captures the a11y hierarchy snapshot + screenshots into the xcresult on failure, but the workflow doesn't upload it. Add an `if: failure()` step uploading `build/DerivedData-test/Logs/Test` as an artifact so failures can be triaged without runner access.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Run 32148: the UI probe fails with an apparently empty accessibility tree — the app reaches Running Foreground but
openAboutBtn(green in run 32029) never materialises. Automation permission is granted on the VM but the hierarchy still appears empty.XCTest already captures the a11y hierarchy snapshot + screenshots into the xcresult on failure, but the workflow doesn't upload it. Add an
if: failure()step uploadingbuild/DerivedData-test/Logs/Testas an artifact so failures can be triaged without runner access.