please find the app attached which I built with minimum number of elements and settings changes to demonstrate the buggy GUI behaviour which I can replicate with ComboBox controls. I didn't further verify if all the App settings and the responsive dimensions of the ComboBox really matter to replicate this bug. I just used the same setup which I currently use for my app development.
The same app is displayed correctly on Android.
Please also see the screenshots attached.
To reproduce the incorrect display behaviour of the app on an iPhone please do the following:
Hi @helgek ,
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. The version of my iOS device is 12.4, the version of PowerApps Mobile Apps is 3.19081.19.
Currently, the lastest PowerApps Mobile App version in iOS device is 3.19081.19. Please consider upgrade your PowerApps Mobile App to the latest version, then try your app again, check if the issue is solved.
Also please consider take a try to turn off the "Improved app rendering (final validation)" option within Advanced settings of App settings of your app, then re-publish your app, try your app again on your iOS device, check if the issue is fixed.
If the issue still exists, please consider run your PowerApps app using lower version of iOS device, e.g. iOS 12.4, then try your app, check if the issue still exists.
thank you for testing my app with the scenario described.
I updated to the latest version of PowerApps (3.19081.19.) on my iOS device and I disabled the improved rendering and republished the app -> The issue remains when I tap on the down arrow of the ComboBox. When I tap into the white space of the ComboBox the editing field doesn't enlarge.
I hope that later today I will have the opportunity to ask a colleague at work not enrolled in iOS 13 to test the app. I will give an additional update then.
I just had the opportunity to test with iPhone 7, iOS 12.2, PowerApps 3.19081.19 and still disabled improved rendering in the settings of the PowerApp. The issue happens exactly in the same way.
Please make sure that you only tap on the down arrow of the ComboBox straight after opening the app. Once you tap into the white space of the ComboBox and you then leave the editing dialog popping up and you then tap on the down arrow of the ComboBox the erroneous behaviour won't occur.
@v-xida-msft, Additional note:
I just tested with an additional ComboBox using Split("test1,test2,test3",",") as Items with only few characters which would not exceed the ComboBox width on a small screen. This also wouldn't avoid the issue.
yes, the issue is still the same. There has also not been any new release of PowerApps for iOS in the meantime which I could have used to test again. Anyway I'm pretty sure that this well reproducable bug (at least here on two company devices with iOS 12 on iPhone 7 and iOS 13 on iPhone 8 Plus) will not disappear easily by coincidence because of other changes in the framework if it is not investigated directly. It has been there over multiple releases of PowerApps for iOS.
There seems to be a specific difference in the PowerApps framework regarding what happens when the user clicks on the editable canvas of the ComboBox compared to when the user clicks on the down arrow of the ComboBox. Of course I don't have any insight into the framework so I might be wrong, but at least from my superficial perspective I would assume that this would be starting point of investigation. What I can of course definitely not comprehend at all is why this strange screen behavior only occurs when the very first element you click on after opening the App is the down arrow segment of the ComboBox. Like I explained before the issue will not occur at all if you e.g. tapped/clicked into the editable canvas of the ComboBox before you tap/click on the down arrow segment of the ComboBox.
I can just say that for my project I'm working on currently and which I plan to roll out to many users in my company this bug is a showstopper for using the App on iOS. I've seen a workaround using TextInput Field instead but since this would not be a nice way of implementation I would definitely prefer to use the ComboBox.
Since my company is a big customer of Office365 I could of course also try to get in touch with you via our Microsoft channels within the company if this would be of help in case you can definitely not reproduce this issue.
Check out the on demand sessions that are available now!
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Features releasing from October 2020 through March 2021
Check out the Power Platform Community Highlights