Well the unfortunate issue is that the bug and various discussions like this one, mix different propblems for people who want the status bar accounted for, but also users that have been doing fullscreen apps, and now see the status bar show up only after some UI interaction like CameraRoll is used. It is unfortunate that Adobe chose to withdrawl that bug without properly addressing and breaking down all the specific cases. yes there are workarounds for some people, depending upon how they want or dont want the status bar. The following specific case still seems unresolved: Where you launch a Stage3D AIR app in fullscreen (successfully not showing any status bar at all on startup). Then later use CameraRoll (causing not only nasty Context3D lost context) but then the status bar text shows up where it didn't before. Yes, we have a 'workaround' (NOT a fix) for this by manually resetting fullscreen mode again after CameraRoll use. (Causing yet a second Context3D lost context). (none of this happens on previous iOS versions, no lost context included) Manually accounting for a status bar area is not a fix for fullscreen apps. It actually undoes what Apple's true intentions were for this new look. They want your app to use the fullscreen and show its contents behind the status bar if present. Shortening the stage viewPort is a workaround but not even the desired result Apple was intending with this feature change. When you see comments like "You need to account for the status bar in your own code". Thats fine, but in this particular case, we started out with no visible status bar, so the "You" in this statement still seems to be Adobe's native code for CameraRoll. I guess now we are forced to try and see if there is a way to use some existing ANE code for Image selection for iOS and see if there is a way to possibly keep the Stage3D view from changing size (avoiding a lost context). If this can be done with an ANE then maybe this will convince Adobe to try and fix this particular use case in their CameraRoll implementation. Otherwise if this can't be done, then we chalk it up to an unpleasant new sideeffect for iOS7 and Stage3D...
... View more