Bug 60667 - Issue with UIPickerView in iPhone X
Summary: Issue with UIPickerView in iPhone X
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.5.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
: 60717 ()
Depends on:
Reported: 2017-11-14 11:46 UTC by Paul Anderson
Modified: 2017-12-20 14:21 UTC (History)
4 users (show)

Tags: uipicker, custom control, ac
Is this bug a regression?: ---
Last known good build:

Sample (1.25 MB, application/zip)
2017-11-14 11:46 UTC, Paul Anderson
Exception Screenshot image (143.66 KB, image/png)
2017-11-14 11:47 UTC, Paul Anderson

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 60667 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Paul Anderson 2017-11-14 11:46:31 UTC
Created attachment 25691 [details]

We have using Syncfusion SfPicker component in Xamarin.forms platform. It work fine in all iOS simulator and devices except iPhone X device and simulator. We have used the picker in a PopUp page. On Clicking the background of the popup page, we get exception in native UITableView datasource.
In Native iOS SfPicker base class is UIPickerView 
Exception detail:
Objective-C exception thrown.Name:NSInternallnconsistencyException
Reason:UITableView datasource is not set.
Replication procedure:
1)Run the sample in iPhone X
2)Click the Header to open Picker page.
3)SfPicker will be visible
4)Click out side to navigate other page.
Exception occur only on iPhone X
We have also attached the exception screenshot image and sample for your reference.
Comment 1 Paul Anderson 2017-11-14 11:47:09 UTC
Created attachment 25692 [details]
Exception Screenshot image
Comment 2 Paul DiPietro [MSFT] 2017-11-14 19:38:03 UTC
I can reproduce this using the sample -- I'm wondering if you only experience this using the SfPicker, or if there's a scenario where you can reproduce the same error with the Forms Picker? I'll leave this as confirmed for now but if this is only on the SfPicker side of things then it may or may not be a problem that lies there.
Comment 3 Paul Anderson 2017-11-15 03:50:08 UTC
The Issue occurs only in Xamarin.Forms iOS version and only with iPhone X simulator and device. The same is working fine in Xamarin.iOS which is the base implementation and using renderer support has been provided to forms. Also we cannot reproduce it with Forms Picker as it will be like a dialog appearing but SfPicker is directly added to PopUp page and only the page acts like a dialog. Also in further debugging on closing the Forms PopUp Page for iPhone X alone LayoutSubViews() gets called which leads to the exception.
Comment 4 Paul DiPietro [MSFT] 2017-11-16 14:00:56 UTC
*** Bug 60717 has been marked as a duplicate of this bug. ***
Comment 5 rohan bethune 2017-11-30 13:27:07 UTC
Do we have an ETA when this will be fixed - this bug prevents us moving forward with Syncfusion and targeting iPhone X.
Comment 6 post4me3 2017-12-20 14:21:16 UTC
@Paul DiPietro  - Seeing this also - iPhoneX device and simulator running 11.x

Tested now with latest XF and get this exception all the time.
Do not see this exception under any other iOS device other then iPhone X.

Do we have a XF build on alpha that fixes this ?