Open Radar

 
Summary:
This issue is related to rdar://21336540.
Using the same scenario, you can end up without a statusbar in Tweetbot *and* an even more problematic compose view.

Steps to Reproduce:
1. Hold phone in portrait mode
2. Open tweetbot so that is show you the main timeline.
3. Rotate phone to landscape mode
4. hit reply on any tweet in the timeline.
5. The compose screen appears, in portrait, with a too wide keyboard (see rdar://21336540). Observe the missing statusbar from on the navigation bar.
6. Hit close.
7.  You return to the timeline, with a reduced height navigation bar and no status bar (see: http://c.inferis.org/image/0G1h0F2g453M/IMG_0043.jpg)

Additionally:
8. make sure the phone did not rotate back to portrait, still keep it in landscape 
9. hit reply on a tweet again
10. compose view comes up, this time with the UI in landscape mode but the keyboard too wide and on the right of the screen: (see: http://c.inferis.org/image/080L0C0l260v/IMG_0042.jpg)

Expected Results:
1. There should be a statusbar visible (as in the original state) and the navigation bar should have a standard height.

Actual Results:
The statusbar should not disappear, nor should the navigationbar be reduced in height.

Notes:
The problem does not go away by going outside the app and back in.
You can revert to a correct visual state by hitting close (after step 10). The main timeline will still be portrait but the statusbar is back and the navigation bar is standard height again.

Not sure if this is UIKit's problem or Tweetbot's problem but since it's easy to reproduce it might be a rotation API issue. I've encountered similar issues before when developing apps, so I feel there's a problem in different rotation settings for view controllers and switching between them.