-
Notifications
You must be signed in to change notification settings - Fork 390
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
unable to access [device's IP]:8100/status when I make Mac and ios17 device connect to same wifi #789
Comments
Interesting, my iPad 17.1 x Xcode 15.1 beta had no issues. My env is still macOS 13, thus possibly the host env could be related. You could try out IPv6, turn mobile connection off etc |
Yes, I have this problem too. I got socket hangup error only GET /status endpoint. I get success with POST /session. |
Did ipv6 work then over the WiFi (not via port forward)? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
than kyou for response. I run the Wda in this path: my appium version 2.3.0 I think these last versions. When i update xcuitest driver, it says STDOUT: STDERR: npm ERR! A complete log of this run can be found in: /Users/burak/.npm/_logs/2024-01-02T19_44_40_308Z-debug-0.log |
it is your local npm caching related. Let me hide past a few comments as not for this original issue |
最后你怎么解决的。 我也是这个问题。 我现在想到的是降低版本 |
Warning:
develop env:
Mac::2019 MacBook Pro, MacOS Sonoma 14.0
Xcode: 15.0
Iphone: Iphone14 Pro ,IOS17.0.3
Appium:2.1.3
Everything work fine When I make iPhone connect Mac via usb.
But when I make iPhone connect Mac via network, the issue arises
I config iPhone connect via network in Xcode, and make sure iPhone and Mac connect to same wifi. Then I build and test wda to iPhone success, the WDA run normal
But I can not access to de url
These issues are not tracked. Please create new issues in the main Appium
repository: https://github.com/appium/appium/issues/new
The text was updated successfully, but these errors were encountered: