Skip to content

[BUG] Infinite edges Android 15 #4576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jesmrec opened this issue Apr 21, 2025 · 1 comment · Fixed by #4581
Closed

[BUG] Infinite edges Android 15 #4576

jesmrec opened this issue Apr 21, 2025 · 1 comment · Fixed by #4581
Assignees
Labels
Estimation - 3 (M) p2-high Escalation, on top of current planning, release blocker Type:bug UI / UX
Milestone

Comments

@jesmrec
Copy link
Collaborator

jesmrec commented Apr 21, 2025

Actual behaviour

After the update to SDK 35, the new feature "infinite edges" causes glitches in the upper and bottom bar of the app. Some examples:

Image Image Image Image

Expected behaviour

Bottom and upper bar does not collide with the Android system bars

Android 15

@JuancaG05 JuancaG05 added this to the 4.6 - Next milestone Apr 24, 2025
@jesmrec jesmrec added the p2-high Escalation, on top of current planning, release blocker label Apr 25, 2025
@JuancaG05
Copy link
Collaborator

Indeed this is change that came with upgrading the target SDK to Android 15, as explained in https://developer.android.com/about/versions/15/behavior-changes-15#edge-to-edge. There, they suggest to adapt component by component with insets, but due to the variety of components we have in the app, this may get a bit complex.

There are other solutions, as the ones suggested in the answers of https://stackoverflow.com/questions/79095037/android-15-edge-to-edge-mode-hide-a-top-view, which may be temporal but enough for the moment.

In any case, this needs deeper research, and one of the next steps could be checking the official Android codelab about how to handle edge-to-edge enforcements.

@joragua joragua self-assigned this Apr 30, 2025
@joragua joragua linked a pull request May 2, 2025 that will close this issue
2 tasks
@joragua joragua removed the Sprint label May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Estimation - 3 (M) p2-high Escalation, on top of current planning, release blocker Type:bug UI / UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants