-
Notifications
You must be signed in to change notification settings - Fork 188
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
[Bug]: IOS Real Device Tests started failing #815
Comments
@agray, have you checked the https://github.com/appium/dotnet-client#compatibility-matrix? |
I am using Selenium 4.23.0 |
And dotnet client version 5.0.0, works for you? |
Could you attache the full Appium server log?
|
Rolled back to Appium 5.0.0 and Selenium 4.22.0 and even less works. (I had originally skipped Selenium 4.22.0.) NUnit Virtual: Tests launch (except IOS Virtual) On Appium 5.1.0 and Selenium 4.23.0: NUnit Virtual: Tests launch |
https://app.saucelabs.com/tests/5988caa82b3d4cbb858bf745f5ca7d24#0 |
It last worked on August 1st: IPhone 15 Pro Max (IOS 17.4.1) I'll even provide the video from SauceLabs: |
So what was the last version that worked for you properly? |
I think it was pre 5.0.0 (or one of the 5 betas) and Selenium 4.21.0 |
Does other webViews works for you? I have no major changes in mind that can cause this. |
Webviews? |
This is appium log from the failed one, 5988ca.... |
It was working on 1st August and I have only updated nuget packages. This code base has worked for many many years. |
https://developer.apple.com/design/human-interface-guidelines/web-views |
worked one:
issue's one:
Your automation used different version of xcuitest driver. I wondered if recent refactoring in remote debugger affected cc @mykola-mokhnach (just to share the remote debugger's thing) Or... https://github.com/appium/appium-xcuitest-driver/blob/master/CHANGELOG.md#7249-2024-08-01 affected the behavior? My recent local test with browserName safari worked though. Need to debug |
Could you test again with XCUITest driver |
I have never specified the version of XCUITest See SauceLabs platform configurator documentation SUT is page hosted by SauceLabs: |
@agray Is the issue persistent, e. g. does it happen always or rather randomly? Are you able to reproduce the issue locally? Could you please provide an example of a failed log with |
Also please review logs attached above - they contain your user name and the access token. I don't think you want these values being shared |
deleted |
Yes its persistent and I get the same exception locally while trying to initialise the driver on line 93 of SauceryBase.cs trying to instantiate a new IOSDriver. This is an integration test so it has to talk to SauceLabs. |
Does it also happen on a single device or multiple devices? Have you tried to reboot the device if it is always the same and run the test again? Eventually, there is also a possibility on Sauce to explicitly provide the Appium snapshot version to run on (https://docs.saucelabs.com/mobile-apps/automated-testing/appium/appium-versions/). You may try to run with an older version to verify the assumption whether the issue has to do with Appium-specific changes |
The "device" is the one requested via DesiredOptions on SauceLabs. SauceLabs spins up a new instance for EVERY test. |
Sorry, my question was a bit different. Do you always request the same device name from your test or every time the test is executed it runs on a different device from the cloud? |
Same type of device, yes. How the selenium grid (which is what SauceLabs is) provides that device it up to the grid and part of the grid "service". |
Lets sum up what needs to be done step by step:
|
Hm, I don't have 17.4.1 but have 17.5.1 iPhone. It returned an empty safari view as below with Possibly the device has a specific condtion |
Any updates on this? |
Did you performed the below steps?
|
I tend to think this is an issue in iOS itself. I was able to reproduce the same behaviour locally with iOS 17.4 and 17.5 Simulators via the Safari remote debugger. Btw, downgrade to 17.2 or 17.3 also did the trick |
Have you? |
Had to rollback to IPhone 14 Pro Max on IOS 16.2 on emulated (IPhone 15 Pro Max on IOS 17.0 just hangs) |
Description
Real Device tests started failing after upgrade to Appium dotnet client 5.1.0 and Selenium 4.23.0 on Saturday 10/08 on SauceLabs.
Environment
Details
SauceLabs tests for iPhone 15 Pro Max Real Device started failing on Saturday 10th August.
Please provide more details, if necessary.
Error returned from SauceLabs: "Status Code: 500 - Error while starting appium session: An unknown server-side error occurred while processing the command. Original error: No webview has been detected after 13926ms."
The text was updated successfully, but these errors were encountered: