iOS Question App Not Compatible with iPadOS 26 Windowing

[jtare]

I have an ios app that presents some issues in iPadOS 26 new windowing system. When users try to arrange multiple apps (like Maps + my app + Music in split layouts), my app doesn't respect the assigned window dimensions and overlaps into other windows.

For what I have seen (or lack thereof) in the forums, and given that iPadOS 26 is an extremely new OS just released. I expected it to not be compatible. My questions are:

1. Has anyone found a workaround for this?
2. Is this a fundamental architecture difference? From how b4i works and how OS 26 expected it to work.
3. If not possible, are there any plans in the future to make it work?

Disclaimer: I have no ipad to test this, I only rely on users feedback to understand this issue

 

[Erel]

I will update on this.

 

[Erel]

I've made some tests with iPadOS 26 beta. Everything seems to work fine. You can see in the video that the layout is resized together with the window. The layout is made of a panel with red border which is anchored to all sides.
You do need to use anchors + designer script + handle B4XPage_Resize event.

 

[jtare]

@Erel Thank you for providing this valuable feedback. One of my app users shared a screenshot with me showing the issue, which for privacy reasons I prefer not to share it as is (personal data is shown). But I censored the windows with private data and attached it here.

I will check the designer script and resize event for any insights.

My best guess is that the user selected the predefined screen split layouts, which ideally would give each app its own window and align them in a grid pattern (left side maps app, right side my app on top and music below).

For context, the app layout inside the window shows fine and properly drawn. But the window seems not to snap into the grid.

It is getting harder to run the iOS simulator on Windows system lately, it uses too many resources (virtualbox + the simulator) and runs extremely slow on a 10th gen intel i7. This is why I cannot reproduce the issue and simulate the iPad behavior.