iOS: Device kit on initial start, starts in wrong order

[wswebcreation]

Mobilewright version

0.0.31

Operating system

MAc

Target platform

iOS

Device or simulator

Sim: iPhone 17 Pro

Minimal reproduction

1. Use the WDIO demo app
2. Have a clean sim, so no device kit is installed

import { test, expect } from '@mobilewright/test';

test('app launches and shows home screen', async ({ screen }) => {
    await expect(screen.getByText('Support')).toBeVisible();
});

test('app opens the Login screen', async ({ screen }) => {
    await expect(screen.getByText('Support')).toBeVisible();
    await screen.getByText('Login').tap();
    // console.log(await screen.viewTree());
    await expect(screen.getByTestId('input-email')).toBeVisible();
    await expect(screen.getByTestId('input-password')).toBeVisible();
    // await screen.getByTestId('input-email').fill('test@test.com');
    await screen.getByPlaceholder('Email').fill('test@test.com');
    await screen.getByPlaceholder('Password').fill('test12345');
    // await screen.getByTestId('input-password').fill('test12345');
    await screen.getByText('LOGIN').tap();
    await expect(screen.getByText('You are logged in!')).toBeVisible();
    await screen.getByText('OK').tap();
});

Actual behavior

• The app starts
• then the device kit starts
• the test starts
• the app under test is not open
• first test times out and fails
• second test can run as intended

This also happens when you remove the Device kit app from the background, see movie that tries all scenarios

recording-startup-error.mp4

Expected behavior

It might be the order the device kit is started

Additional context

No response

[gmegidish]

@wswebcreation that's a good bug.
previous version used simctl spawn instead of launch, and that ran devicekit uitest in the background, but that's really fragile. so we're back to launch. I'll reproduce this and immediately release a version. thanks @wswebcreation !