SfTabView 'Animators may only be run on Looper threads' when changing Tab

[Kien.Phat]

My project have SfTabview with 3 TabItem and it work fine but today when im changing the tab, my App will crash and this error show up

Android.Util.AndroidRuntimeException:** 'Animators may only be run on Looper threads' 

This is debug log:

Loading reference 7 of /storage/emulated/0/Android/data/com.myapp.MyApp/files/.__override__/Syncfusion.SfTabView.XForms.Android.dll asmctx DEFAULT, looking for Syncfusion.Core.XForms, Version=17.4451.0.40, Culture=neutral, PublicKeyToken=null

Assembly Ref addref Syncfusion.SfTabView.XForms.Android[0xdb510460] -> Syncfusion.Core.XForms[0xdb50fd40]: 12

**Android.Util.AndroidRuntimeException:** 'Animators may only be run on Looper threads'

I just remember it's work normally before im update Syncfusion to the last version few days ago.

[Hemalatha Marikumar]

Hi Kien.Phat, 

 

Greetings from Syncfusion. 

 

We would like to let you know that reported crash issue “Android.Util.AndroidRuntimeException when tab between the SfTabview-TabItems” with TabView is a known issue and we have already fixed the same. Please find the patch from below link

Assemblies: 

https://www.syncfusion.com/downloads/support/directtrac/general/ze/SfTabView-1231256426.zip 

 

Assembly Version: 17.4.0.40 

 

Currently we don’t have a patch support for weekly Nuget release. Hence only provided this fix through custom assembly. 

 

Guidelines to use this custom assembly: 

 

Before applying this, please clear the cache 

 

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

 

Please do as per in below link when configured with Nuget in your application 

 

https://www.syncfusion.com/kb/8279/how-to-apply-the-custom-assemblies-when-configured-the-project-with-syncfusion-nuget 

This fix will be included in our weekly Nuget release which is expected to be rolled out on 7^th January 2020. 

 

Regards, 

Hemalatha M. 

 

[Kien.Phat]

Hi Kien.Phat, 

 

Greetings from Syncfusion. 

 

We would like to let you know that reported crash issue “Android.Util.AndroidRuntimeException when tab between the SfTabview-TabItems” with TabView is a known issue and we have already fixed the same. Please find the patch from below link

Assemblies: 

https://www.syncfusion.com/downloads/support/directtrac/general/ze/SfTabView-1231256426.zip 

 

Assembly Version: 17.4.0.40 

 

Currently we don’t have a patch support for weekly Nuget release. Hence only provided this fix through custom assembly. 

 

Guidelines to use this custom assembly: 

 

Before applying this, please clear the cache 

 

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

 

Please do as per in below link when configured with Nuget in your application 

 

https://www.syncfusion.com/kb/8279/how-to-apply-the-custom-assemblies-when-configured-the-project-with-syncfusion-nuget 

This fix will be included in our weekly Nuget release which is expected to be rolled out on 7^th January 2020. 

 

Regards, 

Hemalatha M. 

 

yeah i have followed your guide and when swipe tabview not crashing anymore.

But when tapping Tab header the app will Crash and this showing up:

System.TypeLoadException: Could not resolve type with token 01000039 from typeref (expected class 'System.Drawing.Point' in assembly 'System.Drawing.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51')

[Hemalatha Marikumar]

Hi Kein.Phat, 

 

Thanks for your update. 

 

We have analyzed your query and checked the reported issue of “when tapping Tab header the app will Crash” with our provided custom assembly, but we are unable to reproduce the issue. We have attached sample with our provided custom assembly, please find the sample link from below 

 

Sample link:
https://www.syncfusion.com/downloads/support/directtrac/general/ze/TabViewSwipe-1321563316.zip 

 

We have recorded video for this, please find the video from below link: 

Video link:
https://www.syncfusion.com/downloads/support/directtrac/general/ze/TabException1249252556.zip

 

 

Please check with our provided sample and if issue persists, please update the following details. 

 

·       Update Xamarin.Forms version.

 

·       Update Code snippet or modified sample.

 

This will be helpful for us to investigate further and provide you a better solution at the earliest.

 

Regards, 

Hemalatha M.