-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue when starting Patrol tests on iOS physical (real) device #1828
Comments
Hi @proximilian 👋🏻
Could you clarify this? Do some of them run? Is the moment when they "get stuck" seemingly random? |
For now, I recommend you try out latest dev versions:
I fixed a race condition in this release. It might be the cause of the problem, but if not, we'll keep looking. |
No. After run of 'patrol test' the app was built OK. The test was started successfully and let's say at the first screen it got stuck. So I can't consider the moment as random. |
Hi @bartekpacia
|
Thanks for trying it out – that's actually pretty worrying. But hey, that's why it's on a dev channel. We've seen reports of problems very similar to yours over the last few weeks, but we have not yet found the root cause. The best thing you could do is to try set up a new Flutter app project, set up Patrol for iOS in it, and try to reproduce this issue. If you succeed, share the repo with us, and we'll investigate. Another clarifying question:
|
Hello, @bartekpacia
|
Steps to reproduce
I tried running my Patrol tests on iOS real(physical) device, but hit some problem - please refer to logs. Despite that, all tests are running without any issues at Android devices. Flavors are used as well.
Here is some additional info:
Actual results
Tests start successfully but soon become in waiting state and need to be killed -> refer to log.
Logs
Logs
Patrol version
patrol: 2.3.1
patrol_cli: 2.2.1
Patrol Doctor output
Patrol Doctor output
Flutter Doctor output
Flutter Doctor output
The text was updated successfully, but these errors were encountered: