[Bug?] Information bar on iOS is hidden but still blocks input

[MrNappa]

My canvas app contains a control (component) that is basically a 'title bar' with a back button on it. As such it is always shown on the top of the app. We noticed however that the 'back' button didn't seem to register a click sometimes (leading the user to think the app was unresponsive or buggy).

After some investigation, it appears as though any touch input that is in the area where the 'information bar' (showing the time, battery status, etc) usually appears on iOS, the clicks fail to register.

I tested this with a screen set up as follows:

Each button updates a context variable to toggle the corresponding toggle switch below it.

In my test, the 3rd and 4th button didn't 'click' at all on a device. The first two buttons do, but only if it's pressed not too close to the edge of the screen.

[hopha]

Thank you for reporting this. There are some information we need that might help resolving this faster:

1. Your PowerApps version
2. Your device model (iPhone X, iPad Air, etc.)
3. Your iOS version

Thank you!

[MrNappa]

Thanks!

I observed this on an iPad mini 4 with iOS v13.3 and PowerApps version 3.19114.22.

The app is in landscape orientation with a 4:3 resolution so it matches the device screen size.

[v-yutliu-msft]

Hi @MrNappa ,

I've made a similar test and met the same problem.

However, I found that this is regardless of device and the button's position (whether it is close to edge of the screen).

It is only because of the button being too small.

In my test, I create a button that has very small width, put it in the middle of the screen, test it in my computer.

When I click the button, the button's OnSelect was not triggered.

And I found that when the button's Height/Width  is smaller then 5, it will be hard to trigger the button's OnSelect.

That should be powerapps' limit.

I will report this to our product team.

Thanks for your sharing!

Best regards,

[MrNappa]

Well, while that may be a problem too, it's not the size of the button that was causing this in my app (actual button has a Height of 40 or 50, if I remember correctly). I just used varying button sizes in my test/example in an attempt to better observe the behavior. But thanks for reporting this!