When using the return function in navigation the error is displayed.
Full log attached
at Syncfusion.ListView.XForms.iOS.ExtendedScrollViewRenderer.Dispose (System.Boolean disposing) [0x00009] in <7d0618f1aae248c380f91094422426e9>:0
at Foundation.NSObject.Dispose () [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/220.127.116.11/src/Xamarin.iOS/Foundation/NSObject2.cs:147
at Xamarin.Forms.Platform.iOS.VisualElementPackager.OnChildRemoved (Xamarin.Forms.VisualElement view) [0x0003e] in D:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:122
at Xamarin.Forms.Platform.iOS.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00092] in D:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:200
GPGnana Priya Namasivayam Syncfusion Team March 1, 2019 06:40 PM
Thanks for using Syncfusion support.
We have checked the reported query from our side. We would like to let you know that in our sample we have checked by navigating from one listview page to another by returning particular page in navigation method. Do you mean this “Navigation.Pushasync(new mainpage())” as return function in navigation in your previous update. If yes, then we have attached the tested sample based on your query but reported issue didn’t occur in our sample, please find the sample from below.
Meanwhile, Can you please check whether reported issue occur I our sample also. If no, please revert us back with the modified sample or the replication procedure to reproduce the reported issue which will help us to analyze your query better and provide appropriate solution at our end.
If no, can you please share details like whether you are using any third party plugin to navigate or loading listview inside any other custom view or page. Please explain your use case detail.
Gnana Priya N
TETedMarch 8, 2019 07:43 AM
The example given does not apply to implementation. below that performs the call to page.
var navigationParams = new NavigationParameters();
DYDeivaselvan Y Syncfusion Team March 12, 2019 12:41 PM
We have checked the reported query from our side. We would like to know that when we navigated MainPage with parameters as mentioned, MainPage loaded with properly. We have checked by loading this in App.xaml.cs page instead default prism navigation. We have attached the sample for you reference, please find the sample from below.
If above sample does not meet your requirement, please share more details about how you have done navigation in your sample and please explain your use case in detail which will help us to analyze and provide appropriate solution at our end.