Description:
The Sign In and User Detail screens become non-functional in Landscape Mode
When does this occur?:
When the orientation of device changes to Landscape Mode
attach screenshot / stacktrace:
You can't scroll down to Sign In button and hence can't use the app
You can't enter the details since the detail text field is off the screen, and the screen cannot be scrolled down
As per your understanding what is:
Expected behaviour: Since the Sign In and User Detail Screen of App is not designed to work in Landscape mode, it should be made such that it should not allow Android Framework to Change it's orientation to Landscape.
Actual Behaviour: The Android Framework is able to change the orientation of App into Landscape, which leaves the app completely useless.
The User is unable to even scroll the screen to the Sign In button on first screen
The User can't access the Details too, since it doesn't scroll down.
Steps to reproduce:
1) Clear Cache and Data if already Signed In
2) Change the orientation to Landscape
3) Observe the Bug
Other Comments:
Taking Orientation Control from Android Framework and Setting it as Portrait will fix the issue
We need to add few lines of code to Activities in Android Manifest file to fix the issue
It will not Conflict with the Current Branch or development of the App.
Is it a? (pick one)
Bug Report
Environment
The Bug:
Description: The Sign In and User Detail screens become non-functional in Landscape Mode
When does this occur?: When the orientation of device changes to Landscape Mode
attach screenshot / stacktrace:
You can't scroll down to Sign In button and hence can't use the app
You can't enter the details since the detail text field is off the screen, and the screen cannot be scrolled down
As per your understanding what is:
Steps to reproduce:
1) Clear Cache and Data if already Signed In 2) Change the orientation to Landscape 3) Observe the Bug
Other Comments:
Taking Orientation Control from Android Framework and Setting it as Portrait will fix the issue We need to add few lines of code to Activities in Android Manifest file to fix the issue It will not Conflict with the Current Branch or development of the App.
-Sparsh Srivastava