Questions

New Android build introduces device-specific top safe-area gap / edge-to-edge regression

I’m seeing a reproducible regression in a newly generated Median Android build.

My app is a Base44 web app wrapped with Median. The web app itself has not changed.

Until yesterday, the production Android app rendered correctly edge-to-edge on my physical Pixel 8 Pro and on iPhones.

I generated a new Median Android build after not rebuilding the app for quite a long time. After installing that newer build, certain screens now show a blank area at the top equal to the native status-bar / safe-area height.

I have now been able to reproduce this as an old-build vs new-build comparison on the SAME physical Pixel 8 Pro:

1. I halted the newer Google Play rollout.
2. I uninstalled and reinstalled the app.
3. Google Play installed the previous build.
4. The app rendered correctly edge-to-edge again.
5. Google Play then offered an Update.
6. I installed the newer build.
7. Immediately after updating, the top safe-area gap returned.

Nothing in the Base44 web app changed between these tests.

There are also some important inconsistencies:

• Median's Pixel 9 simulator renders the same new build correctly edge-to-edge.
• Median's Pixel 8 Pro simulator shows the gap.
• My physical Pixel 8 Pro shows the gap.
• iPhone also shows the issue.
• Some components still render edge-to-edge even in the affected build.
• For example, an image hero can show the gap, while a dynamically collapsed coloured header on the exact same page correctly fills the top native area.
• Other screens such as the login screen and some coloured headers also correctly occupy the top area.
• Some full-screen loading content also appears vertically displaced, as though the top inset is now being included differently in viewport/layout calculations.

This makes it look like the newer native wrapper is exposing or handling window/status-bar insets differently, rather than the webpage itself simply having a fixed top margin.

Could you please advise whether anything recently changed in the Android build pipeline regarding:

• target SDK / Android 15+ edge-to-edge behaviour
• WebView window insets
• status-bar overlay
• display cutout handling
• safe-area inset propagation into web content

The previous Median-generated Android build renders the same unchanged web app correctly on the same device, whereas the newer Median-generated build introduces the issue.

I can provide screenshots showing:

• previous build on Pixel 8 Pro: correct full bleed
• newer build on Pixel 8 Pro: top gap
• Pixel 9 simulator: correct full bleed
• Pixel 8 Pro simulator: top gap
• different component states on the same page behaving differently