Skip to content

Commit 58f5634

Browse files
committed
fix(#2682): install the fixture in the target-activation lane
The iOS Smoke job fetches the fixture with `install: 'false'`, and the fixture E2E lane installs it through the public CLI as its first step. The activation lane opened the app instead, so on CI it failed the first step with "The app bundle is not installed on this simulator". It now installs the same way and records that requirement in its own doc comment. Verified live on `apex-2682-proto` with the fixture path pointed at a copy of the installed bundle: the lane passes, including the disclosure assertion and the settled second capture.
1 parent daaf445 commit 58f5634

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎test/integration/smoke-ios-target-activation.test.ts‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,9 @@ import {
1919
* runner response proves the decoder, not the fact.
2020
*
2121
* Runs on the same lanes as the iOS simulator fixture E2E (`smoke` and `full` tiers) and needs the
22-
* same environment: `AGENT_DEVICE_IOS_E2E=1`, `AGENT_DEVICE_IOS_E2E_TIER`, a fixture app already
23-
* installed (`AGENT_DEVICE_FIXTURE_APP_ID`), and `AGENT_DEVICE_IOS_UDID`.
22+
* same environment: `AGENT_DEVICE_IOS_E2E=1`, `AGENT_DEVICE_IOS_E2E_TIER`, `AGENT_DEVICE_FIXTURE_APP_PATH`
23+
* and `AGENT_DEVICE_FIXTURE_APP_ID`, and `AGENT_DEVICE_IOS_UDID`. Those lanes fetch the fixture with
24+
* `install: 'false'`, so this lane installs it through the public CLI like the other fixture lanes do.
2425
*/
2526

2627
const enabled = process.env.AGENT_DEVICE_IOS_E2E === '1';
@@ -34,6 +35,7 @@ test(
3435
async () => {
3536
const context = createContext();
3637
try {
38+
await runStep(context, 'install fixture app', ['install', context.appPath]);
3739
await runStep(context, 'open fixture app', ['open', context.appId]);
3840

3941
// Screenshot is a lifecycle command: it serves whatever is foreground without touching the

0 commit comments

Comments
 (0)