SafariViewService quit unexpectedly.

[LinschotenMelle]

Is there an existing issue for this?

• I have searched the existing issues and didn't find mine.

Steps to reproduce

• maestro test flow.yaml

Actual results

Right now it seems iOS is very flaky and/or incorrect when it comes to dialogs with Flutter.
Whenever im running this script on Android is works as expected, but whenever i use iOS emulator im getting the different result every time I run it. In the end of the second run I get the following error: "SafariViewService quit unexpectedly." which i never got until i used this package.

Im using the following yaml code (can also be seen in the video)

- tapOn: "Email address"
- assertVisible:
    id: "loginDescription"
- tapOn:
    id: "loginDescription"
- waitForAnimationToEnd
- assertVisible:
    id: "loginDescriptionDialog"
- tapOn:
    point: "50%,25%"
- waitForAnimationToEnd
- assertNotVisible:
    id: "loginDescriptionDialog"
- tapOn:
    id: "loginDescription"
- waitForAnimationToEnd
- tapOn:
    id: "ok"
- waitForAnimationToEnd
- assertNotVisible:
    id: "loginDescriptionDialog"
- hideKeyboard

Screen.Recording.2024-12-23.at.2.25.19.PM.mov

What can be the cause of this?

Expected results

The same as Android without flaky instances

About app

The app is a closed source project

• The code can be seen above

About environment

Iphone 15 plus
iOS 18.0

Maestro 1.39.7
 
MacBook Air 13″
macOS 15.2

Logs

Logs

<!-- Replace this line with your logs. *DO NOT* remove the backticks! -->

Maestro version

1.39.7

How did you install Maestro?

Homebrew

Anything else?

No response

[linear]

MA-2841 SafariViewService quit unexpectedly.

[Fishbowler]

This doesn't appear to be something inside Maestro's control. It's polling and sending taps and similar. I wonder if this could be a bug in this version of the simulator, or in this version of iOS under certain circumstances? Have you attempted the same test with iOS 18.2 (available with Xcode 16.2)?

[LinschotenMelle]

@Fishbowler I've upgraded to 16.2 with 18.2 emulator right now and tested the same flow as the video above. I still get the same error.

Is there a way that dialogs should be checked that is different from Android?