Search Issue Tracker

Fixed in 5.2.4

Votes

11

Found in

5.0.1f1

Issue ID

689552

Regression

No

Immersive mode leaves black bar on Nexus 5 when app is re-launched

Android

-

If you are relaunching app through recents screen after Application.Quit(), there is a black bar in place where hardware buttons (back, home, recents) leftover which only can be removed by rotating screen

Comments (7)

  1. alanwant

    Dec 13, 2015 12:15

    So is Unity 5.2.4 unreleased? Did this fix make it into 5.3?

  2. alanwant

    Oct 21, 2015 10:04

    The reason why I think the problem is with Unity is that no other Unity games are doing it. Granted, they may be built using older versions of Unity, but that just proves the point further that Unity can prevent this behavior.

    The only workaround that I have found is to force a change in rotation (using Screen.orientation) to something other than the starting/current orientation, then rotate back. Doing this takes at least a few seconds and looks just awful. It is absolutely out of the question for any professional app.

  3. Macklin

    Oct 20, 2015 16:08

    Also occurs with the Nexus 9 (Android 6.0, Unity 5.2.1f1) on every launch after quitting with Application.Quit() or swiping the app from recents while it is the foreground app. Re-installing the app does not work, forcibly stopping the app does not work. Rotating the device to another orientation or minimizing the app fixes it only for that session.

    I couldn't seem to find a permanent workaround other than restarting the device completely. My bet is it's a problem with Android 6 and not Unity.

  4. ShockFactor

    Oct 18, 2015 17:31

    This bug started for me after upgrading to 6.0 marshmallow(Nexus 5). Tried a system reset to make sure it wasn't an anomaly from the upgrade process. Only way for me to get rid of the black bar is to minimize the app then bring it back.

  5. alanwant

    Oct 17, 2015 11:54

    Severity: 3...."workaround is possible"...I have spent days trying to find a workaround. There is no workaround. Please increase the severity, or explain the workaround.

  6. alanwant

    Oct 17, 2015 03:46

    Tested against every version of Unity after 5.1.1f1 (currently on Unity 5.2.1f1) and the bug still occurs. I have my Nexus 5 updated to Android 6.0 (marshmallow) and have Android SDK v21.

  7. pertsa

    Sep 01, 2015 14:33

    Tested this on Unity 5.1.3f1 and the bug is still there.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.