Berik Visschers

In general: The error is caused by a missing import statement. Import the class that is used and the error will disappear.

Updated the vscode configuration to support debugging. If the vscode configuration is accepted I can add a "debug with vscode" section in the readme.

@aakash1313 I've updated the title and description to match with your finding that the iOS version caused this error. What iOS version did you use to get this error?

Hi @oguzparlak, thanks for the reminder. I tested the addressbook app flow locally on 3 different iOS 16 simulators and a iOS 15 simulator. I could not reproduce the issue....

> Test finishes successfully but as soon as it finishes, It produce this > ... Does maestro produce that message? Maestro now starts idb_companion for you, so you do not...

I've just added logging facilities to maestro to retrieve the idb_companion logs for maestro runs. They have not been released yet, if you want to try them before the release...

On the latest build, maestro will print out the directory where the idb logs can be found. They are zipped. If all of this works, please add them to this...

There is a special homebrew tap for building maestro from source from the main branch, it's called maestro-head. You'd need to uninstall maestro to be able to install it. Another...

Maestro 1.15.0 is released and contains the logging functionality. Could you `brew upgrade maestro`, run the `maestro test` command and then finally run `maestro bugreport` to find the zip file...

Hi @wadey1, maestro version 1.24.0 includes the change you requested. Can you give it a try and let us know what you think?