Android 15 device status bar overlays our app

[hacklschorsch]

Android 15 introduces a new behavior where the device status bar is rendered over our app.

https://developer.android.com/about/versions/15/behavior-changes-15#edge-to-edge

Apps are edge-to-edge by default on devices running Android 15 if the app is targeting Android 15 (API level 35).

Important: If your app is not already edge-to-edge, portions of your app may be obscured and you must handle insets. Depending on the app, this work may or may not be significant.

We track this issue in https://gitlab.com/tahoe-lafs/tahoe-lafs-mobile/-/issues/69 .

Here's an excerpt:

Other cross-platform / full-screen web-view application frameworks suffer from the same problem:

• https://forum.ionicframework.com/t/status-bar-overlaps-the-app-content-help/247967/3

  The overlaysWebView api has bug on Android 15 (Edge to Edge display), Capacitor official documentation has already explained as below [...]

  • Links to https://developer.android.com/reference/android/R.attr#windowOptOutEdgeToEdgeEnforcement
  • Links to https://github.com/capawesome-team/capacitor-plugins/tree/main/packages/android-edge-to-edge-support
• https://forum.framework7.io/t/solved-statusbar-overlapping-the-app/4761
  • https://forum.framework7.io/t/solved-statusbar-overlapping-the-app/4761/8

    I just added preference "Fullscreen" with false status in config.xml

How can I fix our app?

Is this maybe not for here (Obelisk), but for Reflex-Platform?

[adrianmay]

The same thing happens at the bottom of the screen. This renders one of our dialogs inoperable because both the OK and Cancel buttons have the system buttons on top of them, so the system buttons eat all the clicks.

[adrianmay]

Also filed in reflex-platform: reflex-frp/reflex-platform#848

[hacklschorsch]

Version 15 is already the biggest installed base of Android at a bit over 25%, making this rather important for us.

Here's a small update of what we're doing:

• Setting the targetSdkVersion to the (deprecated) version 34 (35 is the new minimum) buys us some time, as that works around the new edge-to-edge default. (bala-lafs-mobile!12)
• Some more time might be bought by opting-out of edge-to-edge for the app. This is only possible in Android 15, and won't be available in Android 16 anymore. (We're currently not planning to do this, I guess an addition to the app's manifest file might be all what's needed? I'll update this thread if we end up implementing this)
• The real fix seems to be to embrace the new edge-to-edge reality and fix our app's UI for it. If using a modern CSS framework, this might be easy or already done for you. We're on Material for the Web version 2, which predates this by much, so we're currently fixing that by hand. https://developer.chrome.com/docs/css-ui/edge-to-edge is a good resource for that. (Our work is happening in bala-lafs-mobile!14)

[maralorn]

That sounds like an important issue. However obelisk is currently in a bit of transitional period with limited maintainer capacities. We are working on migrating from ghc 8.10 to ghc 9.12 but that branch does currently not have android support.

I had a quick glance and I believe the place to fix this would be https://github.com/reflex-frp/reflex-dom/blob/develop/reflex-dom/cbits/MainWidget.c or at least somewhere in reflex-dom.

[hacklschorsch]

Thanks @maralorn ! I have found what could be a very simple and generic fix for this problem. It's currently awaiting testing. I'll update this issue when results are in!

[hacklschorsch]

And happy to hear you're working on GHC 9.12! Hear hear @adrianmay