In iOS v16.2, when we enter inside the SfNumericUpDown and try to change the value manually, the keyboard doesn't show the top section in the second image, which has the "Return" button to the right. And this was working in version 16.1.2.
Thanks in advance,
Thanks for contacting Syncfusion support,
We were unable to reproduce the reported scenario on our side. We used an iPhone 14 Pro Max running iOS 16.2 Simulator for checking the issue. Please review the attached image of the simulator for your reference. If the problem still persists on your end, please provide details about the device or simulator in which the problem occurs, as well as the culture settings, to aid in resolving the reported issue.
Yes, you are right, the error is not happening all the time. In order to eliminate the iPhone and iOS version difference, I decided to use the same one in my test. And I also first decided to use the Syncfusion SfNumericUpDown demo. I just updated all the packages to the final versions and ran it.
Here is the interesting part (which you can also see in the attached video):
Here is another problematic scenario which persists even after the application is closed:
I also get the following output after the one I previously sent you:
2023-01-13 20:09:45.238867+0300 TestApp.iOS[8134:3513699] Can't find keyplane that supports type 8 for keyboard iPhone-PortraitTruffle-DecimalPad; using 27260_PortraitTruffle_iPhone-Simple-Pad_Default
2023-01-13 20:09:48.709706+0300 TestApp.iOS[8134:3513699] [LayoutConstraints] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want.
(1) look at each constraint and try to figure out which you don't expect;
(2) find the code that added the unwanted constraint or constraints and fix it.
"<NSLayoutConstraint:0x600001151900 'accessoryView.bottom' _UIRemoteKeyboardPlaceholderView:0x7fbc0d13e080.bottom == _UIKBCompatInputView:0x7fbbcbf0c470.top (active)>",
"<NSLayoutConstraint:0x60000114e6c0 'assistantHeight' SystemInputAssistantView.height == 45 (active, names: SystemInputAssistantView:0x7fbbf82a6b00 )>",
"<NSLayoutConstraint:0x600001151180 'assistantView.bottom' SystemInputAssistantView.bottom == _UIKBCompatInputView:0x7fbbcbf0c470.top (active, names: SystemInputAssistantView:0x7fbbf82a6b00 )>",
"<NSLayoutConstraint:0x600001151ea0 'assistantView.top' V:[_UIRemoteKeyboardPlaceholderView:0x7fbc0d13e080]-(0)-[SystemInputAssistantView] (active, names: SystemInputAssistantView:0x7fbbf82a6b00 )>"
Query 1: the keyboard doesn't show the top section in the second image, which has the "Return" button to the right
We were able to reproduce the reported issue on our side and we have checked with the framework entry control also, and the same behavior was observed. We will report this behavior to the Xamarin forms team in GitHub and will share the issue link with you on January 19/2023.
Query 2: When I start to enter a number to move focus to the "Add To Cart" button, the keyboard starts behaving weirdly: it moves down but the only upper part stays visible.
It was not an issue and it was the expected behavior when using the physical keyboard of the desktop instead of the onscreen keyboard. So we recommend using the Simulator keypad alone on entering the values.
Query 3: Gettting: Can't find keyplane that supports type 8 for keyboard iPhone-PortraitTruffle-DecimalPad; using 27260_PortraitTruffle_iPhone-Simple-Pad_Default.
We couldn't able to reproduce this exception when deploying the sample. To better understand the root cause and assist with resolving the issue, it would be helpful if you could provide more detailed information about the scenario in which our control was used, including a sample demonstrating the issue with replication steps. Please let us know if you have any other queries.
Query 1: The keyboard doesn't show the top section in the second image, which has the "Return" button to the right
We have reported the "On iOS, The numeric keyboard is displayed without the "return" button while focusing on an entry field" issue to the Xamarin Github team. Please follow the below link for further updates on this issue.