Xamarin.forms: Native crash when using Syncfusion SfListView with Xamarin.Forms 3.5.0.129452

[Giorgi]

Description

Xamarin.Forms 3.5.0.129452 crashes with native crash when using Syncfusion SfListView control

Steps to Reproduce

1. Clone https://github.com/SyncfusionExamples/ListView-GettingStarted-in-Xamarin-Forms
2. Update Syncfusion.Xamarin.SfListView to latest version and update Xamarin.Forms to 3.5.0.129452
3. Run in Release mode.

Expected Behavior

The app works fine and the listview is displayed

Actual Behavior

App crashes

Basic Information

• Version with issue: 3.5.0.129452
• Last known good version: 3.4.0.1029999
• IDE: Visual Studion 2017
• Platform Target Frameworks:
  
  
  
  • Android: 8.1
  
  
• Android Support Library Version: 27.0.2.1

[Giorgi]

Here is the stacktrace:

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...

[marius-bughiu]

Having the same issue. Not linking the SDK assemblies fixes the issue but I ended up with a huge APK. I'm also adding a stacktrace from a debug build (you can reproduce it in debug by not using the shared runtime + linking SDK assemblies).

Also, reproducible with XF 4.0 preview.

Simply rolling back to XF 3.4.0.1029999 solves the problem.

02-18 23:17:01.789 D/Mono (31151): Assembly Ref addref Syncfusion.SfPullToRefresh.XForms.Android[0xe64f1e20] -> Xamarin.Android.Support.SwipeRefreshLayout[0xe640f540]: 3
02-18 23:17:01.815 E/art (31151): JNI DETECTED ERROR IN APPLICATION: negative jsize: -443686848
referenceTable GDEF length=814 1
referenceTable GSUB length=11364 1
referenceTable GPOS length=47302 1
referenceTable head length=54 1
02-18 23:17:01.815 E/art (31151): in call to NewIntArray
02-18 23:17:01.815 E/art (31151): from android.view.View md58432a647068b097f9637064b8985a5e0.FragmentContainer.n_onCreateView(android.view.LayoutInflater, android.view.ViewGroup, android.os.Bundle)
02-18 23:17:01.815 E/art (31151): "main" prio=5 tid=1 Runnable
02-18 23:17:01.815 E/art (31151): | group="main" sCount=0 dsCount=0 obj=0x761414e0 self=0xf48b6a00
02-18 23:17:01.815 E/art (31151): | sysTid=31151 nice=-10 cgrp=default sched=0/0 handle=0xf72c7de4
02-18 23:17:01.815 E/art (31151): | state=R schedstat=( 5251775448 129778313 2725 ) utm=463 stm=62 core=8 HZ=100
02-18 23:17:01.815 E/art (31151): | stack=0xff691000-0xff693000 stackSize=8MB
02-18 23:17:01.815 E/art (31151): | held mutexes= "mutator lock"(shared held)
02-18 23:17:01.815 E/art (31151): native: #00 pc 0034d679 /system/lib/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+204)
02-18 23:17:01.815 E/art (31151): native: #01 pc 0032dfe9 /system/lib/libart.so (_ZNK3art6Thread4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEP12BacktraceMap+148)
02-18 23:17:01.815 E/art (31151): native: #02 pc 0024116f /system/lib/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+902)
02-18 23:17:01.815 E/art (31151): native: #03 pc 00241803 /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortVEPKcS2_St9__va_list+54)
02-18 23:17:01.815 E/art (31151): native: #04 pc 000edf95 /system/lib/libart.so (_ZN3art11ScopedCheck6AbortFEPKcz+28)
02-18 23:17:01.815 E/art (31151): native: #05 pc 000f2f63 /system/lib/libart.so (_ZN3art11ScopedCheck5CheckERNS_18ScopedObjectAccessEbPKcPNS_12JniValueTypeE.constprop.95+5350)
02-18 23:17:01.815 E/art (31151): native: #06 pc 000fc9cd /system/lib/libart.so (_ZN3art8CheckJNI17NewPrimitiveArrayEPKcP7_JNIEnviNS_9Primitive4TypeE+364)
02-18 23:17:01.815 E/art (31151): native: #07 pc 00017a9c (???)
02-18 23:17:01.815 E/art (31151): at md58432a647068b097f9637064b8985a5e0.FragmentContainer.n_onCreateView(Native method)
02-18 23:17:01.815 E/art (31151): at md58432a647068b097f9637064b8985a5e0.FragmentContainer.onCreateView(FragmentContainer.java:33)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.Fragment.performCreateView(Fragment.java:2439)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1460)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1784)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1852)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.BackStackRecord.executeOps(BackStackRecord.java:802)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.FragmentManagerImpl.executeOps(FragmentManager.java:2625)
02-18 23:17:01.815 E/art (31151): at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2411)
02-18 23:17:01.816 E/art (31151): at android.support.v4.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2366)
02-18 23:17:01.816 E/art (31151): at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2273)
02-18 23:17:01.816 E/art (31151): at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:733)
02-18 23:17:01.816 E/art (31151): at android.os.Handler.handleCallback(Handler.java:815)
02-18 23:17:01.816 E/art (31151): at android.os.Handler.dispatchMessage(Handler.java:104)
02-18 23:17:01.816 E/art (31151): at android.os.Looper.loop(Looper.java:207)
02-18 23:17:01.816 E/art (31151): at android.app.ActivityThread.main(ActivityThread.java:5845)

[AmrAlSayed0]

Can I link the SDKs but avoid linking this specific SDKs/namespaces? Would that solve the problem? I am assuming these are the namespaces I should avoid linking "Syncfusion.ListView.XForms"
"Syncfusion.ListView.XForms.Control.Helpers"
"Syncfusion.ListView.XForms.Helpers"
"Syncfusion.SfPullToRefresh.XForms"
"Com.Syncfusion.Sfpulltorefresh"
"Syncfusion.SfPullToRefresh"
"Syncfusion.SfPullToRefresh.Android"
"Syncfusion.SfPullToRefresh.iOS"

Edit:
I looked at this further and the linker needs assembly name not namespaces.
"Syncfusion.SfListView.XForms.dll"
"Syncfusion.SfPullToRefresh.XForms.dll"
"Syncfusion.SfPullToRefresh.Android.dll"
"Syncfusion.SfPullToRefresh.iOS.dll"
According to
https://www.fuget.org/packages/Syncfusion.Xamarin.SfListView
https://www.fuget.org/packages/Syncfusion.Xamarin.SfPullToRefresh
https://www.fuget.org/packages/Syncfusion.Xamarin.SfPullToRefresh.Android
https://www.fuget.org/packages/Syncfusion.Xamarin.SfPullToRefresh.IOS

Edit Again:I tried not linking those assemblies but it still crashed. I am not going to try with this any more and just downgrade to 3.4.

[softsan]

Similar issue here.(works with Xam.forms 3.4 but not in latest 3.5.0.129452 stable)
See attached error logs.
xamform_runtime_error_Android.txt

[marius-bughiu]

@AmrAlSayed0 Syncfusion's assemblies are not SDK assemblies. So I don't think that linking SDK assemblies + the list you provided does anything special. That would work if you were to link user assemblies too.

Based on the stack trace, I believe it's some change in the Android support library, something related to SwipeRefreshLayout?

[DevEddy]

Same issue on Android here. iOS is working fine.

[samhouts]

Please try with 3.5.0.169047. Does this still occur? Thanks!

[bmclane]

Still crashes in release mode. Tested by cloning the project above and updating the Xamarin and Syncfusion libraries.

[GnanaPriyaNamasivayam]

Hi Team,
I have a crash in both debug and release mode also. But if i keep linking option to Don't Link then i could able run my app without crash with xamarin forms 3.5.
But i could run if downgrade to Xamarin.Forms 3.4 without crash in both release and debug mode.
Can you please have a look at this case in debug mode also.

[softsan]

Still having issues. Any updates on this?

[Giorgi]

Any estimate when this will be fixed?

[EmilAlipiev]

Is that linker issue? I have tested in debug mode enabling full linking and it worked fine but if I use full linking in release mode, it crashes. That's bit confusing

[PureWeen]

I reached out to SyncFusion about this one. I haven't been able to narrow down the cause for the crash yet.

From version 3.4 to 3.5 of forms the base class on the ScrollViewRenderer changed from ScrollView to NestedScrollView so SF had to put out a patch for this which for some reason isn't playing nice with 3.5

I recompiled 3.5 and changed the ScrollViewRenderer base class back to ScrollView and when I did that the older version of SF worked fine so there's something with the newest 54 release of SF that doesn't seem to play nicely with XF 3.5

[caseyniemann]

@samhouts confirming this as a blocker for 3.5 and anyone using Syncfusion list view. What is our ETA for a Xam Forms update to resolve

[samhouts]

We're not sure this is something for Xamarin.Forms to fix. It may be something that SyncFusion needs to resolve.

[caseyniemann]

@samhouts From Syncfusion This issue only occurs after Xamarin.Forms update version 3.5 update with linker enabled. As we mentioned, issue occurs because of the Xamarin framework update and we logged issue report (5288) for the same. It can be resolved by setting Linking option as None as we share before.

For now, you can use the earlier Xamarin.Forms (Version 3.4 and earlier) updates to avoid this crashing issue. We are following up with the reported frame work issue and let you know once it is resolved.

We appreciate your patience and please use the earlier Xamarin.Forms updates (3.4 and earlier) until then.

---

[email protected] is the contact. Would appreciate if you two could connect/resolve so we can update. We are on day 15 of not being able to release.

[samhouts]

@caseyniemann We've been in contact with SyncFusion about this matter, and we are working together to resolve it. Thanks

[GnanaPriyaNamasivayam]

Hi Team,
As of now, most of our customers are working by linking as None and this cannot be permanent solution for this crash in release mode. Can you please provide the fix with updated version asap.
We haven't received any of your notifications regarding this issue.

Can you please confirm the issue and share update regarding?

Regards,
Gnana Priya N
(Syncfusion)

[PureWeen]

@GnanaPriyaNamasivayam I emailed Marissa Keller Outten and Christian Grossmann last Thursday and yesterday. That's usually who I contacted whenever I had questions. Should I only ever email support or is there someone else internally I should be emailing to expedite these things?

Can you please set my SF license up with a Source License so that I can compile and debug against SF please? shneuvil at Microsoft dot com is my email address that my current license is against

[caseyniemann]

Hi Team,
As of now, most of our customers are working by linking as None and this cannot be permanent solution for this crash in release mode. Can you please provide the fix with updated version asap.
We haven't received any of your notifications regarding this issue.

Can you please confirm the issue and share update regarding?

Regards,
Gnana Priya N
(Syncfusion)

@samhouts @GnanaPriyaNamasivayam Please connect and resolve, and use the @ sign so you both see this

[Nijamudeen-Mohamed]

@samhouts, Could you please confirm, is there any possibilities of providing an immediate fix for this linker issue in the upcoming Xamarin update?

[samhouts]

We've marked this with our highest priority, and there is communication between SyncFusion and Xamarin engineers. We're working on it. Thanks.

[caseyniemann]

@samhouts @GnanaPriyaNamasivayam does any of this get resolved in the 3.6 Xamarin update?

[samhouts]

@caseyniemann As of right now, we're still seeing the same issues with the latest version of SyncFusion and XF 3.6. It is possible that SyncFusion needs to rebuild against 3.6 in order to resolve this issue. Perhaps @GnanaPriyaNamasivayam or @Nijamudeen-Mohamed can try this and confirm. Otherwise, @PureWeen is scheduled to discuss this directly with SyncFusion on Monday, and we'll have an update then. Thank you for your patience.

[xperseguers]

With XF 3.6 I get compilation errors with FFImage so cannot say :/

[samhouts]

@xperseguers Yep, we're aware of that. https://github.com/luberda-molinet/FFImageLoading/issues/1154#issuecomment-470589841

[EmilAlipiev]

any Progress or ETA for this issue please?

[caseyniemann]

@samhouts @GnanaPriyaNamasivayam We need this resolved, 23 days

[keozx]

24 and XF 3.6 is here, I wonder if Syncfusion will do testing

[PureWeen]

We're narrowing down on an issue with the Android team and working on a way to mitigate the issue for now with SF. Once a solution is in motion I'll post an update.

[caseyniemann]

@samhouts @GnanaPriyaNamasivayam For those expecting 3.6 and the latest of Synfusion to work...it does not. From Syncfusion: The reported issue exists in Xamarin v3.6 also and still this issue not fixed by Xamarin team Xamarin team?

[leonmeijer]

I hope this will be fixed soon. My Android app is now over 100 megabytes in the Play store. Much larger because I disabled the linker.

[georgeinva2004]

If you want to see the sausage making you can track the progress here: https://github.com/xamarin/Xamarin.Forms/projects/32

This particular fix is part of Sprint 150 which is scheduled to complete on 3/29. Unfortunately, there's no way to tell if an actual production-ready fix will be pushed by then.

[mflplatinum]

If you want to see the sausage making you can track the progress here: https://github.com/xamarin/Xamarin.Forms/projects/32

This particular fix is part of Sprint 150 which is scheduled to complete on 3/29. Unfortunately, there's no way to tell if an actual production-ready fix will be pushed by then.

Url fixed: https://github.com/xamarin/Xamarin.Forms/projects/32

[tranb3r]

This particular fix is part of Sprint 150 which is scheduled to complete on 3/29. Unfortunately, there's no way to tell if an actual production-ready fix will be pushed by then.

This is a serious regression, imho it should hot-fixed immediately.
The first step should be to identify the commit in XF3.5 responsible for this regression. Has it been done already ?

[tranb3r]

Still no assignee... what's going on ??

[PureWeen]

At this point we have a plan in place that will involve a release from both sides. There's still some additional testing that needs to be done just to ensure we've dotted and crossed all the things

• Syncfusion is going to push out a release which will make this work for 3.1, 3.2, 3.3, 3.6
• We are working on a hot fix for 3.4 and 3.5 that will make it work for those versions

[Giorgi]

@PureWeen @GnanaPriyaNamasivayam Is there any timeline for these fixes?

[deivaselvan]

@PureWeen @GnanaPriyaNamasivayam Is there any timeline for these fixes?

@Giorgi - Already promised by Xamarin team that this fix will be done within their current sprint and provided timeline on March 29, 2019.
https://github.com/xamarin/Xamarin.Forms/issues/5288#issuecomment-473300702

[keozx]

In their forum thread Syncfusion is still saying is a Xamarin thing, they don't seem to have a release estimate for their change to support 3.6?
https://www.syncfusion.com/forums/142489/compatibility-with-xamarin-forms-3-5

[samhouts]

As @PureWeen said in his comment, this is a coordinated release with SyncFusion. Xamarin is releasing service releases to fix compatibility for 3.4 and 3.5. SyncFusion is releasing a new version that will fix compatibility with 3.5 and 3.6. Hopefully, both Xamarin releases will be available next week. Although we cannot speak to SyncFusion's release schedule, we are aware that this is a high priority for them as well.

There were a lot of variables that went into this issue that made it difficult to determine a course of action that is best for our customers. This will be resolved soon, and we have measures in place to prevent such issues from occuring again. Thank you for your patience!

[ali-h2010]

I tried to ignore the assembly while linking by adding the following to the ignore list but it didn't work.
Syncfusion.SfListView.XForms
I have 2 question:

• Why do Syncfusion's assemblies which is a third party plugin is being linked when i select Link SDK assemblies only?
• Can we ignore all the assemblies under a namespace ?

[EmilAlipiev]

@ali-h2010 because syncfusion tools like sflistview, it doesnt use xamarin forms listview, it is probably using datagrid with custom virtualization pretending to be listview. So xamarin made some breaking changes on datagrid, i presume and broke all the custom tools of Syncfusion. Syncfusion is actually quite ahead of xamarin regarding the tools, for example, drag and drop feature is still not exist in xamarin tools and it is hard to remove dependency of sflistview or sfdatagrid from our apps.

[Nk54]

1 month I face this issue and that I wait for a fix.
I've been telling to my boss that a release will come soon.

I made the mistake to migrate to XF 3.5 without testing in release mode on both platform. My bad, shame on me. Since, I've writtent too much code that relies on XF 3.5 (mostly bindableLayout). I need to make a release and it may be cheaper to remove the SfListView and use the Telerik one instead.
I hope you can give us a fix before the end of next week otherwise, I'll have to migrate to Telerik's ListView which works fine (even if I prefer the SfListView).

Link assemblies set to none didn't fix it neither.
I wish you luck !

[keozx]

Me too, I'm thinking we can actually replace (in our use case) SF List with a custom implementation based on XF 4 CollectionView but will require time

[xperseguers]

This works just fine with the release they did this morning. Did you forget to upgrade? At least with XF 3.6 which is the current stable release.

[leonmeijer]

1 month I face this issue and that I wait for a fix.
I've been telling to my boss that a release will come soon.

I made the mistake to migrate to XF 3.5 without testing in release mode on both platform. My bad, shame on me. Since, I've writtent too much code that relies on XF 3.5 (mostly bindableLayout). I need to make a release and it may be cheaper to remove the SfListView and use the Telerik one instead.
I hope you can give us a fix before the end of next week otherwise, I'll have to migrate to Telerik's ListView which works fine (even if I prefer the SfListView).

Link assemblies set to none didn't fix it neither.
I wish you luck !

My Android with XF 3.5 app and SF .53 works and is in the Play Store. Using these settings:

[keozx]

This works just fine with the release they did this morning. Did you forget to upgrade? At least with XF 3.6 which is the current stable release.

So they already did a major version update which seems to address the issue, cool we will try it thanks for letting us know about the update

[tranb3r]

The question is: why a major version release, while it should have been a simple hot-fix.
Communication around this issue has been such a disaster...
I hope it will work without any new regression, or this time I'm done with SF.

[samhouts]

We apologize for the frustration that this issue has caused. We are committed to preventing such issues in the future, and we're taking steps to prevent regressing third-party controls, such as SyncFusion and Telerik, among others. We value them, and we value our community!

We released 3.4.0.1039999 and 3.5.0.274416 on 2019-03-26 . SyncFusion confirmed with us that these versions no longer crash when tested with their latest version, but I don't know exactly what the SyncFusion version number is.

If you are still experiencing this issue with Xamarin.Forms 3.6 or the versions I've mentioned above, I encourage you to reach out to SyncFusion about the matter (https://www.syncfusion.com/forums/142489/compatibility-with-xamarin-forms-3-5), since I'm not sure they are monitoring this issue any longer. I'm confident that SyncFusion is working hard to get this matter resolved for their customers, and if there is anything else that Xamarin.Forms needs to do, we'll make sure that it's a priority.

Thank you!

[Nk54]

Ok, this morning, I updated to the version of 26 march (the release of today wasn't released yet or nuget cache problem I guess because as I said : I tried with Linking assemblies to none).
I'm glad to confirm it doesn't show a white screen anymore. Thanks !!
I didn't want to use the Telerik ListView as IMHO the SfListView is better.

[softsan]

Tried with Linker mode to Link SDK assemblies only and it doesn't work with Xamarin.forms 3.6.0.264807 and Syncfusion 17.1.0.38 https://help.syncfusion.com/xamarin/release-notes/v17.1.0.38?type=all

[ali-h2010]

same issue. i still am getting a crash and annoying license alerts too.
Thanks SF, you gave it to us for free but you don't have to rub it in our faces.

[caseyniemann]

@samhouts @PureWeen doesn't work with Xamarin.forms 3.6.0.264807 and Syncfusion 17.1.0.38. It's clear from above that the communication between Xamarin and Syncfusion is broken....and has been broken for more than a month and half. Get connected today and get this resolved

[tranb3r]

Same for me. The issue is still here with XF 3.6.0.264807 and SF 17.1.0.38.
It's still not clear to me though if the issue is in XF or SF.
@samhouts @PureWeen Could you please clarify and fix urgently?

[samhouts]

We've reached out to SyncFusion to find out what version they expect the fix to be in. Someone will report back here with that information.

Thank you for your patience!

[keozx]

Wow I was about to update, thanks for letting us know, in their release notes they don't mention the compatibility issue, they seem to reference other 3.5 issues there https://help.syncfusion.com/xamarin/release-notes/v17.1.0.38?type=all
So Xamarin did their job fixing 3.5 but yes 3.6 and above should be fixed by SF side as mentioned before

[EmilAlipiev]

Me too, I'm thinking we can actually replace (in our use case) SF List with a custom implementation based on XF 4 CollectionView but will require time

yes it is possible to create everything of sflistview or sfdatagrid using CollectionView. even if you do custom virtualization, possible with bindable stacklayout or datagrid. this is what syncfusion is doing even though you gave me thumbs down but i am telling you the truth. they arent using ListView of xamarin as inheritance. only thing hard to do is drag and drop feature on sflistview i will be missing

[keozx]

Man I believe you, just thumbed down because then is hard to remove dependency :) which is the ugly thing we all come across

[GnanaPriyaNamasivayam]

We regret for the inconvenience caused.

We have fixed the android linker issue in Sflistview. Currently it could be in testing state, checking on various possible scenarios and list view feature testing. We will complete these testing and update the patch in our upcoming weekly nuget. It could be expected on April 9, 2019. We appreciate your patience until then.

[ali-h2010]

@EmilAlipiev
This solution has drag and drop and advance lists
https://github.com/roubachof/Sharpnado.Presentation.Forms

The question is, will it crash in release mode.
Also, i invested heavily on Syncfusion's listview so it will take some time to rewrite the code.

[GnanaPriyaNamasivayam]

As per the earlier discussion we confirm that fix will be included on our upcoming weekly Nuget scheduled date April 9, 2019 without any further delay. Meanwhile, if you require SfListView Custom Nugets/Assemblies before the weekly Nuget release, please create the support ticket using following link .
To create support : https://www.syncfusion.com/support/directtrac/incidents

Regards,
Gnana Priya N
(Syncfusion Team)

[ali-h2010]

Any update on this issue?

[PureWeen]

@ali-h2010
https://github.com/xamarin/Xamarin.Forms/issues/5288#issuecomment-478209070

[GnanaPriyaNamasivayam]

We are glad to announce that our latest weekly NuGet package update version 17.1.0.40 has been rolled out with the reported issue that “Native crash in release mode with SfListView and Xamarin Forms 3.5 and above” and is available for download (nuget.org).

We thank you for your support and appreciate your patience in waiting for this update.

Regards,
Gnana Priya N
(Syncfusion Team)

[mkieres]

@GnanaPriyaNamasivayam

I just updated SF nugets to latest (17.1.0.40) and on Android I'm seeing an exception when navigating to a page with SfListView on it:

04-10 15:10:04.141 I/MonoDroid(20065): UNHANDLED EXCEPTION:
04-10 15:10:04.157 I/MonoDroid(20065): System.TypeLoadException: Parent class vtable failed to initialize, due to: VTable setup of type Syncfusion.ListView.XForms.Android.Renderer.ScrollViewRenderer failed assembly:/storage/emulated/0/Android/data/Grouping.Droid/files/.__override__/Syncfusion.SfListView.XForms.Android.dll type:ScrollViewRenderer member:(null)
04-10 15:10:04.158 I/MonoDroid(20065): at (wrapper managed-to-native) System.RuntimeType.GetConstructors_native(System.RuntimeType,System.Reflection.BindingFlags)
04-10 15:10:04.158 I/MonoDroid(20065): at System.RuntimeType.GetConstructors_internal (System.Reflection.BindingFlags bindingAttr, System.RuntimeType reflectedType) [0x00008] in <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): at System.RuntimeType.GetConstructorCandidates (System.String name, System.Reflection.BindingFlags bindingAttr, System.Reflection.CallingConventions callConv, System.Type[] types, System.Boolean allowPrefixLookup) [0x00034] in <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): at System.RuntimeType.GetConstructors (System.Reflection.BindingFlags bindingAttr) [0x00000] in <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): 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 <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): 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 <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): at System.Activator.CreateInstance (System.Type type, System.Object[] args) [0x00000] in <58604b4522f748968296166e317b04b4>:0
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Internals.DependencyResolver.ResolveOrCreate (System.Type type, System.Object[] args) [0x00046] in D:a1sXamarin.Forms.CoreDependencyResolver.cs:49
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Internals.Registrar1[TRegistrable].GetHandler (System.Type type, Xamarin.Forms.IVisual visual, System.Object[] args) [0x00051] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:70 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Internals.Registrar1[TRegistrable].GetHandlerForObject[TOut] (System.Object obj, System.Object[] args) [0x0002c] in D:a1sXamarin.Forms.CoreRegistrar.cs:102
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00000] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:336
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:120
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:268
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:92
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:414 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:231
Unhandled Exception:

System.TypeLoadException:

04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:127 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:338 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:120 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:268 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:92 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:414
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:231 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:127
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:338
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:120
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:268
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:92
04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:414 04-10 15:10:04.158 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:231
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:127
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:338
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.AppCompat.Platform.AddChild (Xamarin.Forms.Page page, System.Boolean layout) [0x0000d] in D:a1sXamarin.Forms.Platform.AndroidAppCompatPlatform.cs:350
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.AppCompat.Platform.SetPageInternal (Xamarin.Forms.Page newRoot) [0x000ac] in D:a1sXamarin.Forms.Platform.AndroidAppCompatPlatform.cs:320
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.AppCompat.Platform.SetPage (Xamarin.Forms.Page newRoot) [0x00087] in D:a1sXamarin.Forms.Platform.AndroidAppCompatPlatform.cs:275
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.FormsAppCompatActivity.InternalSetPage (Xamarin.Forms.Page page) [0x00039] in D:a1sXamarin.Forms.Platform.AndroidAppCompatFormsAppCompatActivity.cs:333
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.FormsAppCompatActivity.SetMainPage () [0x00000] in D:a1sXamarin.Forms.Platform.AndroidAppCompatFormsAppCompatActivity.cs:362
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.FormsAppCompatActivity.LoadApplication (Xamarin.Forms.Application application) [0x00282] in D:a1sXamarin.Forms.Platform.AndroidAppCompatFormsAppCompatActivity.cs:138
04-10 15:10:04.159 I/MonoDroid(20065): at Grouping.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in C:UsersmikolajProgrammingReproSfListViewGroupingGroupingGrouping.DroidMainActivity.cs:23
04-10 15:10:04.159 I/MonoDroid(20065): at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <2960acf2eeb24d88b5230e1e8afbdc2e>:0
04-10 15:10:04.159 I/MonoDroid(20065): at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.7(intptr,intptr,intptr)
04-10 15:10:04.179 W/Grouping.Droid(20065): JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
04-10 15:10:04.182 D/Mono (20065): DllImport searching in: '__Internal' ('(null)').
04-10 15:10:04.182 D/Mono (20065): Searching for 'java_interop_jnienv_throw'.
04-10 15:10:04.182 D/Mono (20065): Probing 'java_interop_jnienv_throw'.
04-10 15:10:04.182 D/Mono (20065): Found as 'java_interop_jnienv_throw'.
04-10 15:10:07.132 E/mono (20065):
04-10 15:10:07.132 E/mono (20065): Unhandled Exception:
04-10 15:10:07.132 E/mono (20065): System.TypeLoadException: Parent class vtable failed to initialize, due to: VTable setup of type Syncfusion.ListView.XForms.Android.Renderer.ScrollViewRenderer failed assembly:/storage/emulated/0/Android/data/Grouping.Droid/files/.__override__/Syncfusion.SfListView.XForms.Android.dll type:ScrollViewRenderer member:(null)
04-10 15:10:07.132 E/mono (20065): at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.7(intptr,intptr,intptr)
04-10 15:10:07.132 E/mono (20065): at (wrapper native-to-managed) Android.Runtime.DynamicMethodNameCounter.7(intptr,intptr,intptr)
04-10 15:10:07.132 E/mono-rt (20065): [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Parent class vtable failed to initialize, due to: VTable setup of type Syncfusion.ListView.XForms.Android.Renderer.ScrollViewRenderer failed assembly:/storage/emulated/0/Android/data/Grouping.Droid/files/.__override__/Syncfusion.SfListView.XForms.Android.dll type:ScrollViewRenderer member:(null)
04-10 15:10:07.132 E/mono-rt (20065): at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.7(intptr,intptr,intptr)
04-10 15:10:07.132 E/mono-rt (20065): at (wrapper native-to-managed) Android.Runtime.DynamicMethodNameCounter.7(intptr,intptr,intptr)

The above problem is not related to the topic of this github issue but I figured that I will post it in here anwyays, as I was looking to fix this issue and ran into another...Also it's very fresh and SF people might still be monitoring this thread. The above happens with the Xamarin.Forms 3.5.0.169047 version.

I'm attaching a repro sample. It's an updated SfListView grouping sample that you can find on SF sites. I've tested it on VS 2019 (v 16.0.0).

SfListViewGrouping.zip

EDIT: Confirmed that it doesn't happen in Xamarin.Forms 3.5.0.274416 version

[GnanaPriyaNamasivayam]

We have checked the reported query in the given sample. We would like to inform you that reported crash occurs only in the particular Xamarin version 3.5.0.169047. Is there any specific purpose for using that version because this crash is fixed in all latest versions released after 3.5.0.169047. We recommend you to update the Xamarin Forms version to the latest version to resolve this reported issue.

Regards,
Gnana Priya N
(Syncfusion Team)

[badavid85]

New version (17.1.0.40) works for me with Xamarin.Forms 3.6.0.293080.
Now I am able to build my iOS and Android Apps when Linking SDK Assemblies in Release mode without seeing any native crashes.
Thanks.

[SharbelWired]

I just wanted to chime in that 17.1.0.40 crashes in Xamarin Forms pre-release 4.. I had updated a project to pre-release 4 to test a feature in Prism pre-release (which requires xam 4), and there were still issues with 17.1.0.40. I downgraded everything to Xamarin Forms 3.6.x and the original issue with linking, which is the topic of this thread) is resolved. Just wanted to give a heads up in case someone updates to pre-release 4..

[PureWeen]

@SharbelWired can you post your stack trace?

[GnanaPriyaNamasivayam]

@SharbelWired,

We would like to inform you that Syncfusion Xamarin.Forms components are only compatible with Xamarin Forms stable version. We have mentioned regarding this in our documentation. Please refer our documentation form below link for your reference.

UG Documentation Link : https://help.syncfusion.com/xamarin/introduction/compatibility-road-map

[DineshBabuYadav]

@samhouts , One of our client installed the latest version of Xamarin.Forms v3.6.0.344457 but still he is facing the issue in his application ref Forum.

As per the below commented suggestion, it should resolve in this version.
https://github.com/xamarin/Xamarin.Forms/issues/5288#issuecomment-478075117

Can you please check the issue in this version and revert us asap?

[jrahma]

I am having the same disaster now

SfListView Version 17.2.035

Xamarin Forms version 4.1.0.581479

[bmclane]

@jrahma looks like a bug should be opened with Syncfusion, not Xamarin.
We just started experiencing an OOM crash on Android only in release mode:
Xamarin 3.6.539721
SfListView 17.2.0.35

We are removing Sflistview

[vincentcastagna]

I did not update to XF 4.1, I'm still on 4.0. However, I updated Visual studio to latest 16.2 and I've got a crash on linking with SfListView too. Maybe something linked with new AOT introduced in this version ?

@GnanaPriyaNamasivayam

[xamarindevelopervietnam]

VS 16.2.0
XF Stable 4.1.0.618606
SF 17.2.0.36

I received crash
[MonoDroid] 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
[MonoDroid] at Android.Support.V4.Widget.NestedScrollView.SetOnScrollChangeListener (Android.Support.V4.Widget.NestedScrollView+IOnScrollChangeListener l) [0x0000c] in <1e09550ab4e54a22a61340ec6b5f48a3>:0
[MonoDroid] at Syncfusion.ListView.XForms.Android.ExtendedScrollViewRenderer..ctor (Android.Content.Context context) [0x00007] in <1d13e866db284fb28ce6270fd09fd7e3>:0
[MonoDroid] at (wrapper managed-to-native) System.Reflection.RuntimeConstructorInfo.InternalInvoke(System.Reflection.RuntimeConstructorInfo,object,object[],System.Exception&)
[MonoDroid] at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00005] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] --- End of inner exception stack trace ---
[MonoDroid] at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x0001d] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] at System.Reflection.RuntimeConstructorInfo.DoInvoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0007a] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] at System.Reflection.RuntimeConstructorInfo.Invoke (System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] 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 <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] 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 <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] at System.Activator.CreateInstance (System.Type type, System.Object[] args) [0x00000] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] at Xamarin.Forms.Internals.DependencyResolver.ResolveOrCreate (System.Type type, System.Object source, System.Type visualType, System.Object[] args) [0x000af] in D:a1sXamarin.Forms.CoreDependencyResolver.cs:58
[MonoDroid] at Xamarin.Forms.Internals.Registrar1[TRegistrable].GetHandler (System.Type type, System.Object source, Xamarin.Forms.IVisual visual, System.Object[] args) [0x00052] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:79 [MonoDroid] at Xamarin.Forms.Internals.Registrar1[TRegistrable].GetHandlerForObject[TOut] (System.Object obj, System.Object[] args) [0x0002c] in D:a1sXamarin.Forms.CoreRegistrar.cs:111
[MonoDroid] at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00010] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:342
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:138
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:334
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:110
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:438 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:239
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:127 [MonoDroid] at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00044] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:345 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:138 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:334 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:110 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:438
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:239 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:127
[MonoDroid] at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00044] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:345
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:138
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:334
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:a1sXamarin.Forms.Platform.AndroidVisualElementPackager.cs:110
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:438 [MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer1[TElement].SetElement (TElement element) [0x000e0] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:239
[MonoDroid] at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:a1sXamarin.Forms.Platform.AndroidVisualElementRenderer.cs:127
[MonoDroid] at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Support.V4.App.FragmentManager fragmentManager, Android.Content.Context context) [0x00031] in D:a1sXamarin.Forms.Platform.AndroidPlatform.cs:393
[MonoDroid] at Xamarin.Forms.Platform.Android.AppCompat.FragmentContainer.OnCreateView (Android.Views.LayoutInflater inflater, Android.Views.ViewGroup container, Android.OS.Bundle savedInstanceState) [0x00008] in D:a1sXamarin.Forms.Platform.AndroidAppCompatFragmentContainer.cs:56
[MonoDroid] at Android.Support.V4.App.Fragment.n_OnCreateView_Landroid_view_LayoutInflater_Landroid_view_ViewGroup_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_inflater, System.IntPtr native_container, System.IntPtr native_savedInstanceState) [0x00020] in <8e2cc32557d1415cb7e87025cc8a4a87>:0
[MonoDroid] at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.63(intptr,intptr,intptr,intptr,intptr)
[art] JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_throw'.
[Mono] Probing 'java_interop_jnienv_throw'.
[Mono] Found as 'java_interop_jnienv_throw'.
[MonoDroid] UNHANDLED EXCEPTION:
[MonoDroid] 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
[MonoDroid] at Android.Support.V4.Widget.NestedScrollView.SetOnScrollChangeListener (Android.Support.V4.Widget.NestedScrollView+IOnScrollChangeListener l) [0x0000c] in <1e09550ab4e54a22a61340ec6b5f48a3>:0
[MonoDroid] at Syncfusion.ListView.XForms.Android.ExtendedScrollViewRenderer..ctor (Android.Content.Context context) [0x00007] in <1d13e866db284fb28ce6270fd09fd7e3>:0
[MonoDroid] at (wrapper managed-to-native) System.Reflection.RuntimeConstructorInfo.InternalInvoke(System.Reflection.RuntimeConstructorInfo,object,object[],System.Exception&)
[MonoDroid] at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00005] in <96c0fbcf1c2a46be95325bd99609a594>:0
[MonoDroid] --- End of inner exception stack trace ---
[MonoDroid] at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.63(intptr,intptr,intptr,intptr,intptr)
[MonoDroid] at (wrapper native-to-managed) Android.Runtime.DynamicMethodNameCounter.63(intptr,intptr,intptr,intptr,intptr)
[MonoDroid] at (wrapper managed-to-native) Java.Interop.NativeMethods.java_interop_jnienv_call_nonvirtual_void_method_a(intptr,intptr&,intptr,intptr,intptr,Java.Interop.JniArgumentValue)
[MonoDroid] at Java.Interop.JniEnvironment+InstanceMethods.CallNonvirtualVoidMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue args) [0x00073] in :0
[MonoDroid] at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeNonvirtualVoidMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x0001f] in :0
[MonoDroid] at Android.Views.View.Measure (System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) [0x00035] in <207e29a54396482796911ec489e256ce>:0
[MonoDroid] at Xamarin.Forms.Platform.Android.AppCompat.TabbedPageRenderer.OnLayout (System.Boolean changed, System.Int32 l, System.Int32 t, System.Int32 r, System.Int32 b) [0x0002c] in D:a1sXamarin.Forms.Platform.AndroidAppCompatTabbedPageRenderer.cs:374
[MonoDroid] at Xamarin.Forms.Platform.Android.FormsViewGroup.n_OnLayout_ZIIII (System.IntPtr jnienv, System.IntPtr native__this, System.Boolean p0, System.Int32 p1, System.Int32 p2, System.Int32 p3, System.Int32 p4) [0x00008] in D:a1sXamarin.Forms.Platform.Android.FormsViewGroupobjReleasegeneratedsrcXamarin.Forms.Platform.Android.FormsViewGroup.cs:198
[MonoDroid] at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.41(intptr,intptr,bool,int,int,int,int)

[DineshBabuYadav]

Hello Everyone,

Apologize for the inconvenience.

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
[Syncfusion Team]

[vincentcastagna]

@DineshBabuYadav One can try to skip linking this particular assembly to fix the prob I guess ?

[jrahma]

Hello Everyone,

Apologize for the inconvenience.

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
[Syncfusion Team]

@DineshBabuYadav it's not with SfListView only but with other controls as well. I use SfRototator in my MainPage and now my app is crashing after upgrading to Visual Studio 16.2 and Syncfusion 17.2.036

don't you think a week is a very long time to fix a serious problem which caused a disaster crashing apps?

For example, my client is a semi government organization and others might have business and eCommerce app so that means their whole eOperation on mobile will be stopped for a week?

Appreciate if this will be fixed immediately

[vincentcastagna]

@jrahma it should not affect your end user as you might have released an earlier version of your app with earlier Syncfusion and XF versions. I don't understand your point. This should only affect your local build or staging ones. Unless you published a new version w/o QA test before release but that's another prob 😀.

Sf team has to investigate the prob. Apply a fix and test it. Its ok that it takes a few days

[jrahma]

@jrahma it should not affect your end user as you might have released an earlier version of your app with earlier Syncfusion and XF versions. I don't understand your point. This should only affect your local build or staging ones. Unless you published a new version w/o QA test before release but that's another prob 😀

that's the problem, my earlier app had a problem and I was waiting for the fix which came with a disaster

and the app works fine on all devices and emulators but this problem happens only when installing the app from Google Play

[jrahma]

This is what I am getting in Google Play Console:

java.lang.RuntimeException:
at android.app.ActivityThread.installProvider (ActivityThread.java:6747)
at android.app.ActivityThread.installContentProviders (ActivityThread.java:6289)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6204)
at android.app.ActivityThread.access$1200 (ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1785)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:214)
at android.app.ActivityThread.main (ActivityThread.java:7050)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965)
Caused by: java.lang.ClassNotFoundException:
at dalvik.system.BaseDexClassLoader.findClass (BaseDexClassLoader.java:134)
at java.lang.ClassLoader.loadClass (ClassLoader.java:379)
at java.lang.ClassLoader.loadClass (ClassLoader.java:312)
at android.app.AppComponentFactory.instantiateProvider (AppComponentFactory.java:121)
at android.app.ActivityThread.installProvider (ActivityThread.java:6731)

[DineshBabuYadav]

Hi Everyone,

As promised, we will let you know once the release has been rolled out i.e., July 30, 2019.

@jrahma , we are checking with SfRotator team and will let you know the details asap.

Regards,
Dinesh B

[DineshBabuYadav]

@DineshBabuYadav One can try to skip linking this particular assembly to fix the prob I guess ?

yes, until then you can skip this linking option to resolve the issue at the application itself.

[EmilAlipiev]

hat's the problem, my earlier app had a problem and I was waiting for the fix which came with a disaster

and the app works fine on all devices and emulators but this problem happens only when installing the app from Google Play

what is the difference between testing in release mode and installing from google play? you should be getting this when you run on release also, dont you?
It is strange that I am not having any problem with full linking using xf 4.1.0.581479 and sflistview 17.1.0.52. it is maybe because i am doing my release builds on VS4Mac 2019, Could it be that it is only problem on VS 2019 Windows?

[vincentcastagna]

@EmilAlipiev Well it seems only linked with VS2019 latest. I did not update Syncfusion packages nor Xamarin Forms one, only VS. 16.2.0 introduces a new feat for AOT and bundled assemblies, I guess the error is from here.

[EmilAlipiev]

@vincentcastagna those settings were exist in earlier versions vs 2019 also, at least on enterprise version. Are you talking about community version? those who have problem can they confirm that it is community version of VS?

[xamarindevelopervietnam]

Same problem with VS 16.2.0 and VS for Mac 8.2. Both of them are Enterprise license.

[EmilAlipiev]

Try vs mac 8.3 preview. It works fine for me. I will check vs 16.2 later.

[vincentcastagna]

@EmilAlipiev yep I'm on the community version

[apoiat]

Reporting in. VS2019 16.1.6 / XF 4.1.0.618606 / SfListView 17.2.0.35
Setting Linking to none solves the problem which only appears in release mode.

[iWeaverMan]

VS MAC 8.2 (1105)
XF Stable 4.1.0.618606
SF 17.2.0.36

I received crash
[MonoDroid] 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
[MonoDroid] at Android.Support.V4.Widget.NestedScrollView.SetOnScrollChangeListener (Android.Support.V4.Widget.NestedScrollView+IOnScrollChangeListener l) [0x0000c] in <1e09550ab4e54a22a61340ec6b5f48a3>:0

+1

[EmilAlipiev]

downgrade to 17.1.0.52, it works fine for me in release mode. I tried on VS mac and VS windows latest updates.

[DineshBabuYadav]

Hi Everyone,

Thanks for the patience.

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

[PaulAnderson02]

Hello Everyone,
Apologize for the inconvenience.
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
[Syncfusion Team]

@DineshBabuYadav it's not with SfListView only but with other controls as well. I use SfRototator in my MainPage and now my app is crashing after upgrading to Visual Studio 16.2 and Syncfusion 17.2.036

don't you think a week is a very long time to fix a serious problem which caused a disaster crashing apps?

For example, my client is a semi government organization and others might have business and eCommerce app so that means their whole eOperation on mobile will be stopped for a week?

Appreciate if this will be fixed immediately

@jrahma , Can you please share the stacktrace and details regarding the SfRotator crash issue which will be helpful for us to analyze and resolve at the earliest.

Regards,
Paul Anderson

[xamarindevelopervietnam]

Thanks @DineshBabuYadav it work again!
Kudos Syncfusion Team!

[DineshBabuYadav]

@xamarindevelopervietnam , thanks for the update.

[MuneeshKumarG]

Hello Everyone,
Apologize for the inconvenience.
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
[Syncfusion Team]

@DineshBabuYadav it's not with SfListView only but with other controls as well. I use SfRototator in my MainPage and now my app is crashing after upgrading to Visual Studio 16.2 and Syncfusion 17.2.036

don't you think a week is a very long time to fix a serious problem which caused a disaster crashing apps?

For example, my client is a semi government organization and others might have business and eCommerce app so that means their whole eOperation on mobile will be stopped for a week?

Appreciate if this will be fixed immediately

@jrahma : Can you please share the details of the stacktrace related to Rotator control and the details of the Rotator used in your application which will be helpful for us to analyze and resolve it at the earliest

[jrahma]

Hello Everyone,
Apologize for the inconvenience.
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
[Syncfusion Team]

@DineshBabuYadav it's not with SfListView only but with other controls as well. I use SfRototator in my MainPage and now my app is crashing after upgrading to Visual Studio 16.2 and Syncfusion 17.2.036
don't you think a week is a very long time to fix a serious problem which caused a disaster crashing apps?
For example, my client is a semi government organization and others might have business and eCommerce app so that means their whole eOperation on mobile will be stopped for a week?
Appreciate if this will be fixed immediately

@jrahma : Can you please share the details of the stacktrace related to Rotator control and the details of the Rotator used in your application which will be helpful for us to analyze and resolve it at the earliest

@DineshBabuYadav It's fixed now for all.. Thank you Team