- Home
- Forum
- Xamarin.Forms
- Java.Lang.LinkageError: no method with name='setZ' signature='(F)V' in class Landroid/view/View
Java.Lang.LinkageError: no method with name='setZ' signature='(F)V' in class Landroid/view/View
There seems to be an error with the SF Badge control on android device that was captured in our application crash
Control version:"16.4.0.54"
Device:Galaxy Tab3 10.1
OS:4.4.2
SfBadgeView.AddContent ()
Java.Lang.LinkageError: no method with name='setZ' signature='(F)V' in class Landroid/view/View;
JniEnvironment+InstanceMethods.GetMethodID(Java.Interop.JniObjectReference type, System.String name, System.String signature)
JniType.GetInstanceMethod(System.String name, System.String signature)
JniPeerMembers+JniInstanceMethods.GetMethodInfo(System.String encodedMember)
JniPeerMembers+JniInstanceMethods.InvokeVirtualVoidMethod(System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters)
View.SetZ(System.Single z)
SfBadgeView.AddContent()
SfBadgeView.set_Content(Android.Views.View value)
SfBadgeViewRenderer.OnElementChanged(Xamarin.Forms.Platform.Android.ElementChangedEventArgs`1[TElement] e)
VisualElementRenderer`1[TElement].SetElement(TElement element)
IVisualElementRenderer.SetElement(Xamarin.Forms.VisualElement element)
Platform.CreateRenderer(Xamarin.Forms.VisualElement element, Android.Content.Context context)
VisualElementPackager.AddChild(Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren)
VisualElementPackager.SetElement(Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement)
VisualElementPackager.Load()
VisualElementRenderer`1[TElement].SetPackager(Xamarin.Forms.Platform.Android.VisualElementPackager packager)
VisualElementRenderer`1[TElement].SetElement(TElement element)
IVisualElementRenderer.SetElement(Xamarin.Forms.VisualElement element)
Platform.CreateRenderer(Xamarin.Forms.VisualElement element, Android.Content.Context context)
VisualElementPackager.AddChild(Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren)
VisualElementPackager.SetElement(Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement)
VisualElementPackager.Load()
FrameRenderer.OnElementChanged(Xamarin.Forms.Platform.Android.ElementChangedEventArgs`1[TElement] e)
FrameRenderer.set_Element(Xamarin.Forms.Frame value)
IVisualElementRenderer.SetElement(Xamarin.Forms.VisualElement element)
Platform.CreateRenderer(Xamarin.Forms.VisualElement element, Android.Content.Context context)
VisualElementPackager.AddChild(Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren)
VisualElementPackager.SetElement(Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement)
VisualElementPackager.Load()
VisualElementRenderer`1[TElement].SetPackager(Xamarin.Forms.Platform.Android.VisualElementPackager packager)
VisualElementRenderer`1[TElement].SetElement(TElement element)
IVisualElementRenderer.SetElement(Xamarin.Forms.VisualElement element)
Platform.CreateRenderer(Xamarin.Forms.VisualElement element, Android.Content.Context context)
VisualElementPackager.AddChild(Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren)
VisualElementPackager.SetElement(Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement)
VisualElementPackager.Load()
VisualElementRenderer`1[TElement].SetPackager(Xamarin.Forms.Platform.Android.VisualElementPackager packager)
VisualElementRenderer`1[TElement].SetElement(TElement element)
IVisualElementRenderer.SetElement(Xamarin.Forms.VisualElement element)
Platform.CreateRenderer(Xamarin.Forms.VisualElement element, Android.Support.V4.App.FragmentManager fragmentManager, Android.Content.Context context)
FragmentContainer.OnCreateView(Android.Views.LayoutInflater inflater, Android.Views.ViewGroup container, Android.OS.Bundle savedInstanceState)
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)

Bharathiraja K [Syncfusion]
Replied On April 23, 2019 11:15 AM UTC
Hi Vadim,
Sorry for the inconvenience caused.
We can reproduce the reported issue in Android version 4.4 devices. However,we have confirmed this as an issue and we will include this fix in our upcoming weekly NuGet which is scheduled to be roll out on 30thApril,2019.We appreciate your patience until then.
Feedback link:https://www.syncfusion.com/feedback/5941
You can now track the status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Regards,
Bharathi.
SIGN IN To post a reply.
2 Replies
BK
Bharathiraja K
Syncfusion Team
April 23, 2019 11:15 AM UTC
Hi Vadim,
Sorry for the inconvenience caused.
We can reproduce the reported issue in Android version 4.4 devices. However, we have confirmed this as an issue and we will include this fix in our upcoming weekly NuGet which is scheduled to be roll out on 30th April,2019. We appreciate your patience until then.
Feedback link: https://www.syncfusion.com/feedback/5941
You can now track the status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Regards,
Bharathi.
BK
Bharathiraja K
Syncfusion Team
May 3, 2019 10:41 AM UTC
Hi Vadim,
We are glad to announce that our weekly NuGet was rolled out today and fix for the reported issue was included in the weekly NuGet.
NuGet Version: 17.1.0.43
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.
Regards,
Bharathi.
SIGN IN To post a reply.
- 2 Replies
- 2 Participants
-
VK Vadim Koystinen
- Apr 17, 2019 11:59 PM UTC
- May 3, 2019 10:41 AM UTC