appium / appium-flutter-driver

Appium Flutter Driver is a test automation tool for Flutter apps on multiple platforms/OSes. Appium Flutter Driver is part of the Appium mobile test automation tool maintained by community
MIT License
470 stars 183 forks source link

Encountered internal error running command: Error: No observatory URL matching to '/(Observatory listening on |An Observatory debugger and profiler on\s.+\sis available at: |The Dart VM service is listening on )((http|\/\/)[a-zA-Z0-9:/=_\-.\[\]]+)/' was found in the device log. Please make sure the application under test is configured properly according to https://github.com/appium/appium-flutter-driver#usage and that it does not crash on startup. #739

Open ChandanMySelenium opened 2 months ago

ChandanMySelenium commented 2 months ago

can any one help me to solve this please

dlewis2017 commented 1 month ago

I'm running into this problem as well. Maybe the wording has changed when you start up flutter in latest so it can't find it. I'm not great at grep but:

A Dart VM Service on My iPad is available at: http://127.0.0.1:65015/Aaj81SrdP9Y=/ The Flutter DevTools debugger and profiler on My iPad is available at: http://127.0.0.1:9102?uri=http://127.0.0.1:65015/Aaj81SrdP9Y=/

Versus what appium is looking for: '/(Observatory listening on |An Observatory debugger and profiler on\s.+\sis available at: |The Dart VM service is listening on )((http|\/\/)[a-zA-Z0-9:/=_-.[]]+)/' was found in the device log

You've commented on a lot of other posts similar to this one, I'm curious as to your thoughts on this idea? @KazuCocoa

I've also updated to iOS 18 recently on my device and MacOS 15

KazuCocoa commented 1 month ago

One thing we could advise is if the device prints the log of the URL in the syslog. appium:showIOSLog capability would help to check it.

dlewis2017 commented 1 month ago

I did a few things and one of them seemed to work. It was either:

  1. After restarting my Mac. I found that flutter run --profile was actually failing (where it didn't show that before) 2.My flutter channel was a little behind. There were some unstaged changes so I had to abort them and then run flutter upgrade