Notification center quick reply presents keyboard upside down covering the reply field

Originator:m4ttcheetham
Number:rdar://24765740 Date Originated:22-Feb-2016 09:02 AM
Status:Duplicate of 24454206 (Closed) Resolved:
Product:iOS Product Version:9.2.1 (13D15)
Classification:UI/Usability Reproducible:Always
 
Summary:
When using an app that supports upside down orientation in said orientation and receiving a notification (such as iMessage) that supports quick reply it is impossible to reply as the keyboard presents from the top of the screen upside down and covers the notification and input field.

Steps to Reproduce:
1. Open an app that supports upside down orientation (I used Waze)
2. Turn phone upside down
3. Have someone send an iMessage to the phone
4. Notification centre pops down from the top as expected with the message
5. Pull down on the notification to get the quick reply field
6. Keyboard is presented over top of notification upside down
7. Cannot reply, only way to get out is to press home button to dismiss the keyboard/notification

Expected Results:
Keyboard should present from bottom of screen in correct orientation

Actual Results:
Keyboard is presented from top of screen down as if the phone is in portrait mode the right way up.

Regression:
I have only been able to test this on my iPhone 6s on iOS 9.2.1 but I am able to recreate every time

Comments

Apple Developer Relations

Thank you for contacting us.

The original report on this issue, Bug ID 24454206, is still under investigation. There is no release in testing with a fix yet.

We will do our best to keep you informed as new information becomes available. Please check release notes regularly for changes affecting this issue.

If you have further questions about this issue or wish to check on the status, please update your report again using the Apple Bug Reporter http://bugreport.apple.com.

By m4ttcheetham at March 9, 2016, 7:38 a.m. (reply...)

m4ttcheetham

The bug that you have marked this bug as a duplicate as is listed as closed. As this is not resolved in the latest beta could you please provide information on what the resolution of the duplicate ticket is. Thanks.

By m4ttcheetham at March 4, 2016, 9:27 a.m. (reply...)

Apple Developer Relations

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.

If you have any questions or concerns, please update your report directly here: http://bugreport.apple.com/.

By m4ttcheetham at March 4, 2016, 9:26 a.m. (reply...)

m4ttcheetham

Still reproducible on 9.3 Beta 5

By m4ttcheetham at March 2, 2016, 8:35 a.m. (reply...)

Apple Developer Relations

[Marked as Duplicate of 24485891 (Closed)]

This ticket remains open

By m4ttcheetham at March 2, 2016, 8:35 a.m. (reply...)

m4ttcheetham

I am still able to reproduce this on 9.3 Beta 4.

I've attached a video of this occurring on a device running 9.3 Beta 4.

'upsideDown.mov' was successfully uploaded.

By m4ttcheetham at March 1, 2016, 1:56 p.m. (reply...)

Apple Developer Relations

1) Does this still reproduce in the latest 9.3 seed?

2) If so, can you user provide a screenshot or video of reproduction so we can follow your timing?

To provide screenshots or a screen recording showing the issue: https://developer.apple.com/bug-reporting/ios/misc/#screenshots

Please provide your response or results by updating your bug report. If uploading files, please compress first.

By m4ttcheetham at March 1, 2016, 11:54 a.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!