Compatibility with Xamarin Forms 3.5

[Unknown]

Are there any issues known with lately released XF 3.5?

Since the update our App throws on Android (emulator in this case):

02-06 11:18:01.981 I/mono-stdout(26814): 11:18:01.9788 Fatal System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.

02-06 11:18:01.981 I/mono-stdout(26814):   at Syncfusion.ListView.XForms.Android.ExtendedScrollViewRenderer.GetScroller (System.String assemblyname, Java.Lang.Object scrollview, Android.Widget.OverScroller overscroller) [0x00042] in <189d4c4aa2964421bf0435ac19996583>:0 

02-06 11:18:01.981 I/mono-stdout(26814):   at Syncfusion.ListView.XForms.Android.ExtendedScrollViewRenderer..ctor (Android.Content.Context context) [0x0001e] in <189d4c4aa2964421bf0435ac19996583>:0 

02-06 11:18:01.982 I/mono-stdout(26814):   at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke(System.Reflection.MonoCMethod,object,object[],System.Exception&)

02-06 11:18:01.982 I/mono-stdout(26814):   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00005] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.982 I/mono-stdout(26814):    --- End of inner exception stack trace ---

02-06 11:18:01.982 I/mono-stdout(26814):   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x0001a] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.982 I/mono-stdout(26814):   at System.Reflection.MonoCMethod.DoInvoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0007a] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.982 I/mono-stdout(26814):   at System.Reflection.MonoCMethod.Invoke (System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.982 I/mono-stdout(26814):   at System.RuntimeType.CreateInstanceImpl (System.Reflection.BindingFlags bindingAttr, System.Reflection.Binder binder, System.Object[] args, System.Globalization.CultureInfo culture, System.Object[] activationAttributes, System.Threading.StackCrawlMark& stackMark) [0x0022b] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.982 I/mono-stdout(26814):   at System.Activator.CreateInstance (System.Type type, System.Reflection.BindingFlags bindingAttr, System.Reflection.Binder binder, System.Object[] args, System.Globalization.CultureInfo culture, System.Object[] activationAttributes) [0x000a1] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.983 I/mono-stdout(26814):   at System.Activator.CreateInstance (System.Type type, System.Object[] args) [0x00000] in <d4a23bbd2f544c30a48c44dd622ce09f>:0 

02-06 11:18:01.983 I/mono-stdout(26814):   at Xamarin.Forms.Internals.DependencyResolver.ResolveOrCreate (System.Type type, System.Object[] args) [0x00046] in D:\a\1\s\Xamarin.Forms.Core\DependencyResolver.cs:49 

02-06 11:18:01.983 I/mono-stdout(26814):   at Xamarin.Forms.Internals.Registrar`1[TRegistrable].GetHandler (System.Type type, Xamarin.Forms.IVisual visual, System.Object[] args) [0x00051] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:70 

02-06 11:18:01.983 I/mono-stdout(26814):   at Xamarin.Forms.Internals.Registrar`1[TRegistrable].GetHandlerForObject[TOut] (System.Object obj, System.Object[] args) [0x0002c] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:102 

02-06 11:18:01.983 I/mono-stdout(26814):   at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:327 

[...]

Best regards, Ulrich

[Emil]

I have the same problem on device also. can we take this please as high priority? 

[Gnana Priya Namasivayam]

Hi Emil, 

 

We would like to know that this exception occurs after updating Xamarin.Forms version to 3.5. SfListView will not reproduce any crash up to Xamarin.Forms version 3.4, so you can use SfListView with XF 3.4. We are currently validating this issue with XF 3.5 and will provide further details on February 8,2019 . We will appreciate your patience until then. 

 

 

 

Regards,  

Gnana Priya N  

  

[Emil]

Hi,

yes, i simply updated to 3.5 using v16.4.0.48 of sflistview. deleted bin, obj, nuget and rebuild my app. it works on uwp but crashes on Android. I havent tried v16.4.0.52 yet but it definetly crashes using v16.4.0.48. please make sure that you are using all latest android support libraries as well.

thanks,

Emil

[Cepega]

I was updating XF to last version and SFControls (sfListView, stTabView, sfBackdrop, sfButton) to the last version and had the same error.

When I restored my code from git with the previous version it was working fine.

[Besir]

SF Carousel and SF Button is crashing with Same Nullreference Exception at Forms 3.5 version, while they were working steady with earlier versions. 

[Gnana Priya Namasivayam]

Hi Besir, 

 

 

We have confirmed that reported issue “Target invocation exception occurs when Xamarin forms version upgraded to 3.5” is a defect in SfListView and logged a defect report for this bug. The fix will be included in our upcoming weekly nuget release on February 13, 2019 and for other controls will validate and provide further details on or before Febrauary 12, 2019. 

  We will appreciate your patience until then.  

 

 

Regards, 

Gnana Priya N 

[Philippe Leybaert]

This is not limited to SfListView. SfPopupLayout also crashes with Xamarin.Forms 3.5.0

[Emil]

Hello,

please check UWP also. Although it is not crashing, nothing works. listview isnt displayed correctly and other tools also.

thanks,

Emil

[Jayaleshwari N]

Hi Emil,  

  

We have checked the reported query with sflistview and sfpopuplayout from our side. In UWP, app seems to work well and also touch passes to sflistview properly without any issue. If you are using any other control other than listview and popup, then please mention. We have attached the tested sample in which we have used both controls, please find the sample for your reference.  

  

Sample Link : http://www.syncfusion.com/downloads/support/forum/142489/ze/ListViewsample826029609   

 

Can you please check with the above sample whether issue occurs in our sample also. If no, please revert us back with the issue reproducible sample with replication procedure which help us analyze the query better and provide appropriate solution at our end.  

 

# Regarding Crash with SfPopupLayout 

We have already found and logged issue report for the mentioned issue “Throws error when setting template to the Popup Layout” in Xamarin.Forms update version 3.5. The issue occurs only when the project Xamarin.Forms update version above 3.5 and it is not occurring the previous updates.   

  

We will fix this issue and include the issue fix in our upcoming Volume 1 main release update and it will be expected to be available by mid of March 2019.   

  

You can now track the status of this issue and contact us for any further inquiries through this link,  

  

https://www.syncfusion.com/feedback/4668/popupview-is-crashed-while-loading-when-when-contenttemplate-is-assigned-in-xamarin-forms-version-3-5  

 

Regards,  

Jayaleshwari N 

[Bertrand]

Hi,

Could you please confirm that a fix for the SfListView crash with XF3.5 will be included in the weekly nuget release on February 13, 2019 ?

Thanks

Bertrand

[Jayaleshwari N]

Hi Bertrand, 

 

Sorry for the inconvenience.  

There is a delay in weekly nuget release. It will be released within this weekend (February 2 week, 2019). We appreciate your patience until then. 

 

Regards, 

Jayaleshwari N. 

[Jayaleshwari N]

Hi There, 

  

We are glad to announce that our latest weekly NuGet package update version 16.4.0.53 has been rolled out with the fix included for the issue “Target invocation exception occurs when Xamarin forms version upgraded to 3.5” and is available for download. 

 

We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance. 

  

Regards, 

Jayaleshwari N 

[Bertrand]

It works for me.

Thank you.

Bertrand

[Marcel]

Hi There, 

  

We are glad to announce that our latest weekly NuGet package update version 16.4.0.53 has been rolled out with the fix included for the issue “Target invocation exception occurs when Xamarin forms version upgraded to 3.5” and is available for download. 

 

We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance. 

  

Regards, 

Jayaleshwari N 

App still crashing on release build on version 16.4.0.53

For me too

[Aaron Coppock]

Same, crashing with XF3.5 and .53 of syncfusion

[Emil]

Hi Guys,

provided 53 version works for sflistview. please define here which of the nuget package doesnt work for you. Make sure that you clean bin, obj folders and rebuild your app.

[Marcel]

Hi Guys,

provided 53 version works for sflistview. please define here which of the nuget package doesnt work for you. Make sure that you clean bin, obj folders and rebuild your app.

I´m working to discover

• SFListView               ✓
• SfPopUpLayout        ✓
  
• SfButton                    ✓
  
• SfCalendar                 ✓

• SFTabView               X
  

I have SfTabView in a Detail page of MasterDetailPage. 

All TabItens.Contents are  ContentViews with specific ViewModels. 

In my content view I have setted 

<ContentView.BindingContext>

     <viewModel:MyViewModelName>  

</ContentView.BindingContext>

When execute on android, all subcontrol in ContentView are binding to my DetailPageViewModel

[Jayaleshwari N]

Hi There, 

 

Can you please update the details about the crash which still occurs in your application more detailed information like in which control you are facing issue with replication procedure. 

 

# Regarding SfTabView crash  

 

We are able to reproduce the reported issue and the fix will be included in our next weekly nuget update version which is estimated to be available within middle of the next weekend. We appreciate your patience until then. 

 

Regards, 

Jayaleshwari N. 

[Marcel]

Here is a sample of the error of SfTabView.

When run on android, you can see this error in the debug output window:

[0:] Binding: 'MyText2' property not found on 'SampleError.MainPageViewModel', target property: 'Xamarin.Forms.Label.Text'

Attachment: SampleError_1925dcf3.zip

[Marcel]

Hi Guys,

provided 53 version works for sflistview. please define here which of the nuget package doesnt work for you. Make sure that you clean bin, obj folders and rebuild your app.

Find details below:

Using:

Android Device and Emulator

Syncfusion.Xamarin.SfListView 16.4.0.53

Xamarin Forms Stable 3.5.0.129452

Steps and Result:

1. Run on debug mode app run's fine.

2. Run on release mode app crash.

3. Removed control SfListView from view and run on release mode app run's fine.

4. Tried clean, rebuild, deleted bin and obj folder from all projects, run on release mode app crash.

Maybe the error is not with SfListView. But with the controls in the DataTemplate.

[Kurt Ziegler]

The latest nuget fixed my problem with SfListView, am now able to upgrade to Forms 3.5.  Thanks for the quick turnaround.

[Marcel]

Hi Guys,

provided 53 version works for sflistview. please define here which of the nuget package doesnt work for you. Make sure that you clean bin, obj folders and rebuild your app.

Find details below:

Using:

Android Device and Emulator

Syncfusion.Xamarin.SfListView 16.4.0.53

Xamarin Forms Stable 3.5.0.129452

Steps and Result:

1. Run on debug mode app run's fine.

2. Run on release mode app crash.

3. Removed control SfListView from view and run on release mode app run's fine.

4. Tried clean, rebuild, deleted bin and obj folder from all projects, run on release mode app crash.

Maybe the error is not with SfListView. But with the controls in the DataTemplate.

May be, but that should not works on debug mode too.

Here is my SfListView declaration in XAML:

 <sfListview:SfListView Grid.Row="0" HeightRequest="130" ItemSize="120"  x:Name="listView" ItemsSource="{Binding DataReport}"
                                   Orientation="Horizontal" BackgroundColor="White">
                <sfListview:SfListView.ItemTemplate>
                    <DataTemplate>
                        <Grid Padding="10">
                            <Grid.RowDefinitions>
                                <RowDefinition Height="*" />
                                <RowDefinition Height="*" />
                            </Grid.RowDefinitions>
                            <Label Grid.Row="0" Text="{Binding Name}" HorizontalOptions="FillAndExpand" HorizontalTextAlignment="Center" Style="{StaticResource LabelStyleSmall}"/>
                            <Label Grid.Row="1" Text="{Binding Value}" HorizontalOptions="FillAndExpand" HorizontalTextAlignment="Center" Style="{StaticResource LabelStyleLarge}" TextColor="Black"/>
                        </Grid>
                    </DataTemplate>
                </sfListview:SfListView.ItemTemplate>
            </sfListview:SfListView>

Try to remove {Binding Name} and {Binding {Value} for your labels and put a fixed "Text1" and "Text2". 

[Giorgi Dalakishvili]

Crashes in Release mode for me as well

[Giorgi Dalakishvili]

The app crashes with the following stacktrace:

02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470] JNI DETECTED ERROR IN APPLICATION: negative jsize: -443686848
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]     in call to NewIntArray
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]     from android.view.View md58432a647068b097f9637064b8985a5e0.FragmentContainer.n_onCreateView(android.view.LayoutInflater, android.view.ViewGroup, android.os.Bundle)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470] "main" prio=5 tid=1 Runnable
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   | group="main" sCount=0 dsCount=0 obj=0x75bb0268 self=0xf4305400
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   | sysTid=10889 nice=0 cgrp=default sched=0/0 handle=0xf7582534
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   | state=R schedstat=( 0 0 0 ) utm=1014 stm=158 core=1 HZ=100
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   | stack=0xff4e7000-0xff4e9000 stackSize=8MB
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   | held mutexes= "mutator lock"(shared held)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #00 pc 00351799  /system/lib/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+128)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #01 pc 00331cb5  /system/lib/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMap+304)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #02 pc 0023a07f  /system/lib/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+846)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #03 pc 0023a5b7  /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortVEPKcS2_St9__va_list+58)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #04 pc 000ca893  /system/lib/libart.so (_ZN3art11ScopedCheck6AbortFEPKcz+42)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #05 pc 000ca841  /system/lib/libart.so (_ZN3art11ScopedCheck17CheckNonHeapValueEcNS_12JniValueTypeE+164)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #06 pc 000c94ff  /system/lib/libart.so (_ZN3art11ScopedCheck22CheckPossibleHeapValueERNS_18ScopedObjectAccessEcNS_12JniValueTypeE+130)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #07 pc 000c8969  /system/lib/libart.so (_ZN3art11ScopedCheck5CheckERNS_18ScopedObjectAccessEbPKcPNS_12JniValueTypeE+800)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #08 pc 000cfcb9  /system/lib/libart.so (_ZN3art8CheckJNI17NewPrimitiveArrayEPKcP7_JNIEnviNS_9Primitive4TypeE+452)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   native: #09 pc 0002722c   (???)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at md58432a647068b097f9637064b8985a5e0.FragmentContainer.n_onCreateView(Native method)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at md58432a647068b097f9637064b8985a5e0.FragmentContainer.onCreateView(FragmentContainer.java:33)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.Fragment.performCreateView(Fragment.java:2261)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1419)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1750)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1819)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.BackStackRecord.executeOps(BackStackRecord.java:797)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.executeOps(FragmentManager.java:2590)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2377)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2332)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2239)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:700)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.os.Handler.handleCallback(Handler.java:751)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.os.Handler.dispatchMessage(Handler.java:95)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.os.Looper.loop(Looper.java:154)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread.main(ActivityThread.java:6776)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at java.lang.reflect.Method.invoke!(Native method)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1496)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1386)
02-17 14:55:33.843 F/art     (10889): art/runtime/java_vm_ext.cc:470]
02-17 14:55:34.064 F/art     (10889): art/runtime/runtime.cc:419] Runtime aborting...

[Giorgi Dalakishvili]

I cloned SyncfusionExamples/ListView-GettingStarted-in-Xamarin-Forms

updated to Xamarin.Forms 3.5, updated to latest version of Syncfusion Nuget packages and got the exact same error:

02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470] JNI DETECTED ERROR IN APPLICATION: negative jsize: -443686848
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]     in call to NewIntArray
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]     from void md5e6dceb8716288c40551f253cf2268d49.MainActivity.n_onCreate(android.os.Bundle)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470] "main" prio=5 tid=1 Runnable
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   | group="main" sCount=0 dsCount=0 obj=0x75bb0268 self=0xf4305400
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   | sysTid=18225 nice=0 cgrp=default sched=0/0 handle=0xf7582534
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   | state=R schedstat=( 0 0 0 ) utm=278 stm=41 core=3 HZ=100
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   | stack=0xff4e7000-0xff4e9000 stackSize=8MB
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   | held mutexes= "mutator lock"(shared held)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #00 pc 00351799  /system/lib/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+128)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #01 pc 00331cb5  /system/lib/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMap+304)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #02 pc 0023a07f  /system/lib/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+846)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #03 pc 0023a5b7  /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortVEPKcS2_St9__va_list+58)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #04 pc 000ca893  /system/lib/libart.so (_ZN3art11ScopedCheck6AbortFEPKcz+42)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #05 pc 000ca841  /system/lib/libart.so (_ZN3art11ScopedCheck17CheckNonHeapValueEcNS_12JniValueTypeE+164)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #06 pc 000c94ff  /system/lib/libart.so (_ZN3art11ScopedCheck22CheckPossibleHeapValueERNS_18ScopedObjectAccessEcNS_12JniValueTypeE+130)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #07 pc 000c8969  /system/lib/libart.so (_ZN3art11ScopedCheck5CheckERNS_18ScopedObjectAccessEbPKcPNS_12JniValueTypeE+800)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #08 pc 000cfcb9  /system/lib/libart.so (_ZN3art8CheckJNI17NewPrimitiveArrayEPKcP7_JNIEnviNS_9Primitive4TypeE+452)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   native: #09 pc 000166cc   (???)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at md5e6dceb8716288c40551f253cf2268d49.MainActivity.n_onCreate(Native method)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at md5e6dceb8716288c40551f253cf2268d49.MainActivity.onCreate(MainActivity.java:29)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.Activity.performCreate(Activity.java:6955)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1126)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread.-wrap14(ActivityThread.java:-1)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.os.Handler.dispatchMessage(Handler.java:102)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.os.Looper.loop(Looper.java:154)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at android.app.ActivityThread.main(ActivityThread.java:6776)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at java.lang.reflect.Method.invoke!(Native method)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1496)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1386)
02-17 17:44:49.406 F/art     (18225): art/runtime/java_vm_ext.cc:470]
02-17 17:44:49.560 F/art     (18225): art/runtime/runtime.cc:419] Runtime aborting...

[Sangeetha Raju]

Hi Giorgi, 

 

We have checked in our source regarding the crash issue when upgraded to latest Xamarin forms version in SfListView Xamarin Forms. We have already found and fixed similar issue when upgraded to latest xamarin forms in SfListView. The fix for this issue has been included in our latest weekly NuGet package update version 16.4.0.53 and is available for download.  

 

Please clear the NuGet cache before install this package. 

 

https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache  

 

Could you please check with the mentioned SfListView nuget version at your end and let us know if you face any issue.Else kindly revert us back with issue following details, SfListView version used,issue producing patforms.It will be helpful for us to analyze and provide you solution. 

 

Regards, 

Sangeetha Raju 

[Jeff Weber]

I'm also having issues when upgrading to sfListView 16.4.0.53 and Xamarin Forms 3.5.0.129452.

Prior to upgrading, my screen that uses sfListView works fine on all platforms.

After upgrading, my screen that uses sfListView works fine on UWP, but throws the following when running on Android:

"System.NullReferenceException: Object reference not set to an instance of an object."

If I fall back to the previous release of Xamarin Forms, all platforms work again.

I have tried clearing bin/obj, cleaning solution, un-installing app on device 1st, and clearing the nuget cache... nothing worked for me.

-Jeff

[Giorgi Dalakishvili]

Hi Giorgi, 

 

We have checked in our source regarding the crash issue when upgraded to latest Xamarin forms version in SfListView Xamarin Forms. We have already found and fixed similar issue when upgraded to latest xamarin forms in SfListView. The fix for this issue has been included in our latest weekly NuGet package update version 16.4.0.53 and is available for download.  

 

Please clear the NuGet cache before install this package. 

 

https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache  

 

Could you please check with the mentioned SfListView nuget version at your end and let us know if you face any issue.Else kindly revert us back with issue following details, SfListView version used,issue producing patforms.It will be helpful for us to analyze and provide you solution. 

 

Regards, 

Sangeetha Raju 

I uninstalled the Syncfusion package, cleared bin/obj, cleared nuget cache, reinstalled the nuget and I still get the same crash with the same stacktrace.

[Gnana Priya Namasivayam]

Hi There,  

 

We have updated our sample to latest version with SfListView 16.4.0.53 and XF 3.5. Unfortunately , reported issue didn’t occur at release mode in Android platform. Can you please share the call stack from SfListView when your sample crashed which will help us to analyze the query better and provide appropriate solution from our end.  

 

We have attached the tested sample four your reference, please find the sample from below.  

 

Sample Link : http://www.syncfusion.com/downloads/support/forum/142489/ze/GettingStartedSample1656389459   

 

Can you please check whether reported issue occurs in our sample also. If no, please revert us back with the modified sample or with the replication procedure to reproduce the reported issue.  

 

Regards,  

Gnana Priya N  

 

[Giorgi Dalakishvili]

Here are the changes I made in GettingStarted.Android project properties under Release configuration:

On the 'Android Options' page I turned off 'Use Shared Runtime' and under the Linking option I switched to 'Sdk Assemblies Only' options. This causes the app to crash. There is no managed exception occurring, it crashes with native exception.

See the full stacktrace at syncfusion crash stacktrace (starting from line 40)

It does not crash if I set Linking to None but it results in large apk

[Giorgi Dalakishvili]

I also created an issue at Xamarin github repo

[Jayaleshwari N]

Hi Giorgi,  

  

We have checked the attached full call stack. We would like to know that crash didn’t occur from syncfusion assemblies, so we are currently following up the reported bug to xamarin framework. We will update you once we get to know any of solutions to overcome this issue.  

  

Link :  https://github.com/xamarin/Xamarin.Forms/issues/5288   

  

As of now you can run in release mode with None as Linking option to avoid reported crash.   

  

Regards,  

Jayaleshwari N 

[Emil]

Here are the changes I made in GettingStarted.Android project properties under Release configuration:

On the 'Android Options' page I turned off 'Use Shared Runtime' and under the Linking option I switched to 'Sdk Assemblies Only' options. This causes the app to crash. There is no managed exception occurring, it crashes with native exception.

See the full stacktrace at syncfusion crash stacktrace (starting from line 40)

It does not crash if I set Linking to None but it results in large apk

 
Did you try to attach source code of xamarin forms and see why it is crashing? does linker remove some functions in your libraries? maybe we can have a workaround with skip assemblies option?

[Jayaleshwari N]

Hi Emil,  

We would like to let you know that based on the call stack provided exception seems to occur from native element. We haven’t get any notification from Xamarin source while loading in release mode and also while skipping assemblies. We are currently following up with the reported bug, we will let you know once they update on this issue. Meanwhile, you also can tract the status of the reported bug for further response.  

   

Regards,  

Jayaleshwari N 

[Emil]

Is there any Progress on that issue? there is now 3.6 Version. are we able to use it in release mode with full linking?

[Deivaselvan Y]

Hi Emil, 

 

We would like to inform that the crash in release mode was confirmed as bug by Xamarin team and they have promised to fix it on or before March 29,2019. You can track the status of this issue from the below link.
https://github.com/xamarin/Xamarin.Forms/issues/5288  

 

Regards,  

Deivaselvan 

[ulysses]

having that same issue with xamarin forms 4.0

[Dinesh Babu Yadav]

Hi Ulysses, 

 

Could you please share the stacks trace for the reported issue? So, that we could able to provide you an appropriate solution. 

 

Regards, 

Dinesh Babu Yadav 

[Kenny Dinh]

I reported in this topic: https://github.com/xamarin/Xamarin.Forms/issues/5288#issuecomment-514979910

[Dinesh Babu Yadav]

Hi Kenny, 

 

Thanks for the update. We have already logged a defect report for the reported issue and the fix will be included in our upcoming weekly Nuget i.e., July 30, 2019. We will appreciate your patience until then. 

 

Regards, 

Dinesh Babu Yadav 

[Kenny Dinh]

Hi Dinesh Babu Yadav,

I'm glad to hear that!

[Dinesh Babu Yadav]

Hi Kenny, 

 

We are glad to announce that our latest weekly NuGet package update version 17.2.0.39 has been rolled out and the reported issue has been resolved and it is available for download (nuget.org).        

 

We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance.     

 

Regards, 

Dinesh Babu Yadav