-
Notifications
You must be signed in to change notification settings - Fork 299
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
Incorrect element locations on iOS 18.1 Simulator #2138
Comments
@BrandonYuen, we also encountered this issue, and it doesn't seem to be tied to the OS version. We experienced it even on iOS 16 while working with a React Native application. Interestingly, the correct coordinates are returned when using simulators like the iPhone SE with a fingerprint touch (HOME button). It would be helpful if the Maestro team could investigate this to ensure compatibility across all simulator types. After debugging the Maestro iOS driver, I found that the issue stems from the following code, which returns incorrect element coordinates: Line 182 in 5cbe049
|
@herval can anyone look into this issue, please? it is good if this layout works in all type of devices. |
@herval Could you provide some insight on whether this will be supported in the future or if there are no plans for it? Also, is this issue specific to XCUITest, or is there a workaround to make it work? |
Same issue goes for me... |
Is there an existing issue for this?
Steps to reproduce
maestro studio
Actual results
tapOn doesn't work so I investigated with
maestro studio
and as you can see below, the element locations (boxes) are incorrect.Expected results
Locations (boxes) of elements should be correct.
As a fix I downloaded and installed a iOS 16.4 Simulator which does not have this issue. It's the same exact code and context, just swapped the simulator.
About app
Closed source
About environment
Macbook m4, iOS simulator 18.1
Logs
No response
Maestro version
1.39.1
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
No response
The text was updated successfully, but these errors were encountered: