Save/Update/Finish Button hidden by status bar

[corayana]

Hi,
I just started using your app and am pretty happy so far.
One issue that bothers me is that the app reaches under the status bar on my phone (Google Pixel 4a). This makes it very difficult to save/update or finish a session. I would bei very happy you could fix this.

[LiamMorrow]

Thanks for the report! It definitely shouldn't be doing that, I'll see what I can do

[LiamMorrow]

Would you be able to tell me your android version please?
You can find it by going into your phone's settings, scrolling to "System" then tapping "About Phone"

Thank you!

[corayana]

Thank you for the quick response. My android version is 13.

[LiamMorrow]

Fantastic. I'll have a play with the emulator tonight to see what I can do.

[LiamMorrow]

I cannot for the life of me get this bug to show up I'm afraid. I have a workaround, which would just amount to offsetting the top by a static distance. I'll release a new version with this toggle which should help you in the meantime.

[corayana]

Thank you very much for your efforts! Unfortunately, I have no idea what the problem might be.
Anyway, the workaround works so far, at least for ending a session (but not for creating/editing a new/existing session)

[LiamMorrow]

Yeah it's a headscratcher. You say it doesn't work for creating/editing sessions. Could you show me a screenshot of what you mean? It should apply everywhere

[LiamMorrow]

Also, do you have developer mode enabled? If so, would you be able to show your WebView implementation? I wonder if it's a browser version issue...

[LiamMorrow]

LiftLog/LiftLog.Maui/Platforms/Android/MainActivity.cs

Line 55 in 30b2530

ViewCompat.SetOnApplyWindowInsetsListener(

This is where I perform the calculation to get the insets. It works on all emulators and my phone (asus zenfone 9).

[spar34vi]

I'm getting the same issue on Pixel 7 pro (android 15)

[LiamMorrow]

I've got a clue! Seems like I can reproduce it when using a non english language (thanks for the translation @spar34vi!) I have a feeling I know exactly what it is now... I think that the inset is resolving to a decimal, and I am formatting it for the css using the region's format (i.e. commas). But CSS is not regionalised, and it REQUIRES periods.

A fix for this will be inbound! 🎉 Thanks for all the reports!