-
Notifications
You must be signed in to change notification settings - Fork 273
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
Landscape support for iOS #565
Comments
I have the same issue. I have an app that only runs in landscape mode on iPad and maestro mismatches all the elements. If I test with portrait orientation, everything works. |
Hey guys, somebody knows if there is any progress regarding this issue? |
I'm having the same issue for an Ipad app that is mainly used in landscape mode. |
Hi there! 👋 |
Hi, this is something we'd like to add but we can't provide an ETA yet. We'll update this thread with news. |
I have the same issue with an Ipad app mainly used in landscape mode. |
What is the status with this? It should be set with a high priority. |
same issue. we have a video player we can toggle to fullscreen and all the elements are mismatched in maestro studio |
Still no updates? Is there any roadmap of the project? |
This is fine in android but in iOS was not fine, it will just complete the steps but not executed in the emulator. See video. @ArthurSav Untitled_.Jul.18.2023.3_36.PM.webm |
any updates? |
I have issue with Android tablet in Maestro Cloud (everything is fine in local). |
I have the same issue. When is this going to be worked on? |
Is there any news on this feature? It's really preventing us to use Maestro for our UI tests. |
+1 |
have the same issue on iPad in landscape orientation, any updates? |
Hello, when do you think that landscape support will be in your pipeline? With the new European Legal Regulations on Accessibility, applications will need to support landscape by June 2025. It would be great to be able to test in landscape at least a couple of month before. Thanks |
@barbaramartina Thanks for this interesting insight. We are aware this problem is important for you; it's in our backlog. For tracking purposes: there's a related issue #1679 |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
re-opening as this had to be reverted in v1.37.9 |
good day, any movement with this issue, really looking forward to this fix |
We'll release this soon as part of Maestro version 1.39. |
Thanks. When is the version going to be released? |
Either tomorrow or next week. |
The currently available draft version doens't reflect the latest master. Let me relase a new one in a few minutes. |
Please check out # before doing this, uninstall all existing maestro versions
brew update
brew install [email protected] |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
@klyovan Please create a new issue (and reference this one) |
iOS testing currently does not support landscape mode. (I am not sure about the current status of landscape support with Android)
As a quick test, download the samples:
And update the iOS flow to:
Launch the simulator and rotate into landscape mode, and then run:
The test reports that it passes, but it does not navigate into the search screen to type into the text.
Running
maestro studio
shows a mismatch where the overlay content appears to be laid out in landscape, but the image of the app's screen is rotated 90 degrees:NOTE: This was discussed in a couple of slack threads, but I'm adding a ticket here so myself and anyone else interested can follow along for status updates or to be notified when support is available.
The text was updated successfully, but these errors were encountered: