Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native crash when using Syncfusion SfListView with Xamarin.Forms 3.5.0.129452 #5288

Closed
Giorgi opened this issue Feb 17, 2019 · 72 comments

Comments

@Giorgi
Copy link

commented Feb 17, 2019

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 Giorgi added the t/bug 🐛 label Feb 17, 2019

@pauldipietro pauldipietro added this to New in Triage Feb 17, 2019

@Giorgi

This comment has been minimized.

Copy link
Author

commented Feb 17, 2019

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: #1 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: #2 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: #3 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: #4 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: #5 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: #6 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: #7 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: #8 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: #9 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

This comment has been minimized.

Copy link

commented Feb 18, 2019

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: #1 pc 0032dfe9 /system/lib/libart.so (_ZNK3art6Thread4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEP12BacktraceMap+148)
02-18 23:17:01.815 E/art (31151): native: #2 pc 0024116f /system/lib/libart.so (ZN3art9JavaVMExt8JniAbortEPKcS2+902)
02-18 23:17:01.815 E/art (31151): native: #3 pc 00241803 /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortVEPKcS2_St9__va_list+54)
02-18 23:17:01.815 E/art (31151): native: #4 pc 000edf95 /system/lib/libart.so (_ZN3art11ScopedCheck6AbortFEPKcz+28)
02-18 23:17:01.815 E/art (31151): native: #5 pc 000f2f63 /system/lib/libart.so (_ZN3art11ScopedCheck5CheckERNS_18ScopedObjectAccessEbPKcPNS_12JniValueTypeE.constprop.95+5350)
02-18 23:17:01.815 E/art (31151): native: #6 pc 000fc9cd /system/lib/libart.so (_ZN3art8CheckJNI17NewPrimitiveArrayEPKcP7_JNIEnviNS_9Primitive4TypeE+364)
02-18 23:17:01.815 E/art (31151): native: #7 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

This comment has been minimized.

Copy link

commented Feb 19, 2019

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

This comment has been minimized.

Copy link

commented Feb 19, 2019

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

This comment has been minimized.

Copy link

commented Feb 20, 2019

@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

This comment has been minimized.

Copy link

commented Feb 20, 2019

Same issue on Android here. iOS is working fine.

@samhouts

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

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

@bmclane

This comment has been minimized.

Copy link

commented Feb 22, 2019

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

@samhouts samhouts added this to the 3.5.0 milestone Feb 22, 2019

@samhouts samhouts moved this from New to Ready For Work in Triage Feb 22, 2019

@samhouts samhouts added this to To do in Sprint 149 via automation Feb 22, 2019

@samhouts samhouts added this to Ready in v3.5.0 Feb 22, 2019

@GnanaPriyaNamasivayam

This comment has been minimized.

Copy link

commented Feb 22, 2019

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

This comment has been minimized.

Copy link

commented Feb 23, 2019

Still having issues. Any updates on this?

@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Feb 26, 2019

@Giorgi

This comment has been minimized.

Copy link
Author

commented Feb 27, 2019

Any estimate when this will be fixed?

@EmilAlipiev

This comment has been minimized.

Copy link
Contributor

commented Feb 28, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Feb 28, 2019

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

@samhouts samhouts moved this from Needs Estimate to Ready For Work in Triage Mar 2, 2019

@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Mar 2, 2019

@samhouts samhouts moved this from Needs Estimate to Ready For Work in Triage Mar 2, 2019

@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Mar 2, 2019

@keozx

This comment has been minimized.

Copy link

commented Mar 29, 2019

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 comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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:
2019-03-29 16_49_23-Window

@keozx

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link
Member

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

@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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link
Member

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2019

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

This comment has been minimized.

Copy link

commented Mar 29, 2019

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

@GnanaPriyaNamasivayam

This comment has been minimized.

Copy link

commented Mar 30, 2019

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

This comment has been minimized.

Copy link

commented Apr 1, 2019

@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

This comment has been minimized.

Copy link

commented Apr 1, 2019

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

This comment has been minimized.

Copy link

commented Apr 8, 2019

Any update on this issue?

@PureWeen

This comment has been minimized.

Copy link
Contributor

commented Apr 8, 2019

@GnanaPriyaNamasivayam

This comment has been minimized.

Copy link

commented Apr 9, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Apr 10, 2019

@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:\a\1\s\Xamarin.Forms.Core\DependencyResolver.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:\a\1\s\Xamarin.Forms.Core\Registrar.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:\a\1\s\Xamarin.Forms.Platform.Android\Platform.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:\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:\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:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.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:\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:\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:\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:\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:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.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:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.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:\a\1\s\Xamarin.Forms.Platform.Android\Platform.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:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\Platform.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:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\Platform.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:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\Platform.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:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\FormsAppCompatActivity.cs:333
04-10 15:10:04.159 I/MonoDroid(20065): at Xamarin.Forms.Platform.Android.FormsAppCompatActivity.SetMainPage () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\FormsAppCompatActivity.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:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\FormsAppCompatActivity.cs:138
04-10 15:10:04.159 I/MonoDroid(20065): at Grouping.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in C:\Users\mikolaj\Programming\Repro\SfListViewGrouping\Grouping\Grouping.Droid\MainActivity.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

This comment has been minimized.

Copy link

commented Apr 10, 2019

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

This comment has been minimized.

Copy link

commented Apr 10, 2019

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.

@samhouts samhouts moved this from To do to Closed in v3.6.0 Apr 22, 2019

@SharbelWired

This comment has been minimized.

Copy link

commented Apr 25, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Apr 25, 2019

@SharbelWired can you post your stack trace?

@GnanaPriyaNamasivayam

This comment has been minimized.

Copy link

commented Apr 25, 2019

@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

This comment has been minimized.

Copy link

commented May 15, 2019

@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.
#5288 (comment)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.