You appear to have your navigation set to swipe which hides the navigation bar. Set your phone's navigation to three button and see if it's still works.
Just wondering if you are using swipe or three-button navigation? I'm using three button navigation. Swipe navigation might not have the problem
I am aware we can do some/most/all of that using extensions, but hoping, beyond hope, that if MIT have something to fix on this, then they can fix this too
We shouldn't have to use an extension to handle a fundamental display issue as raised by the OP.
Thanks. This helped a lot. Now I see the problem.
A strongly educated guess is that the formula used to calculate the available screen space when all are percentages is not taking the new insets calculation into account.
I can work with that.
It looks like the workaround is to set at least one arrangement height to fill parent.
Does that cover the stretching reported by the OP?
ETA: Actually, I think it might.
Yes, as I showed, but it would be helpful if you could provide the bar heights and "usable" screen height (which could change depending on which bars are visible).
As it stands, there is no logic to setting % arrangement heights that add up to 100% if they do not completely show on screen.
I didn't hide the Navbar (as you can see), but the Title bar (Action bar).
I'm away from the computer right now, but I'm pretty sure before when everything was working and using the older app inventor, I had the main button arrangement to fill parent and it would adjust correctly to the navigation bar. Then after the updated app inventor, it didn't work
For now, I'm using an extension to hide the status /navigation bar, and use a fake status bar to eliminate the problem of the hole punch camera messing up the title button. Notice I got all my 15 rows of buttons back.
Interesting, I just tried this. Arrangement a 10%, Arrangement b 75%, Arrangement c Fill Parent.
In companion, Arrangement c is obscured by the Nav Bar (3 button). (Methinks 75% is too much for the available visible screen, my available screen height is 84% of actual screen height)
Yes, I understand. I'm working on a bugfix. A workaround would be useful until I have one.
I suspect that the %s are calculating from the screen height without offsets across the board, so they'll be slightly off until the fix is out.
Edit, the screenshot interferes so it doesn't show all buttons, but they're there when out of screenshot mode
I think we all know who's causing and responsible for these new problems. And I fear this "edge-to-edge" nonsense won't spare us the use of extensions or absurd workarounds. I'll just remind you of the ridiculous behavior of the keyboard covering the Texbbox, which I already posted today.
Could you share your project with me via PM so I can load it into the test environment where I'm working on the fix?
If crash rate High Becouse of " status bar " changes..Use this : Status Bar Regulator Extension : FREE - #2 by MJ_BUNNY_T.V - Extensions - Niotron Community
Using the showstatusbar block unfortunately shows the navigation bar as well. I need to just hide navigation while still showing the status bar
I get an error when trying to import
Never mind, figured out gdrrive's wierd downloads