-
-
Notifications
You must be signed in to change notification settings - Fork 236
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 change orientation #443
Comments
What device did you use and could you share the logcat?
I haven't seen such behaviors in my experience. Perhaps your device and logcat may help to see some behaviors. |
1.Running Scripts on BrowserStack video-9f15ca81285132853fd28948fa8f8e790aaac5d5.mp40 expected: "landscape"
[cucumber] Failing Scenarios: 1 scenario (1 failed) Appium Log : |
2.Running scripts on Emulator Given I login as anonymous user Error: Screen rotation cannot be changed to ROTATION_270 after 2000ms. Is it locked programmatically? (Selenium::WebDriver::Error::ElementNotInteractableError) Failing Scenarios: 1 scenario (1 failed) |
3.Running same script on Real Device(Redmi 9) Error 1: Error 2: |
I don't have Redmi 9, but found its 8. It worked the orientation command on my env.
Then please ask for their support first. Potentially their environment has some limitations.
https://stackoverflow.com/questions/39387158/i-am-getting-error-while-trying-to-check-orientation-of-app said the case could happen when the app refused to orientation or it depends on the sensor. |
set auto screen rotate to OFF in my android device. But when I run Appium automation, it gets set to ON somehow. Is there a way to prevent Appium from setting auto screen rotate to ON?
An unknown server-side error occurred while processing the command. Original error: Set the orientation, but app refused to rotate. (Selenium::WebDriver::Error::UnknownError)
UnknownError: An unknown server-side error occurred while processing the command. Original error: Set the orientation, but app refused to rotate.
@ruby @appium
The text was updated successfully, but these errors were encountered: