- Home
- Forum
- Xamarin.Android
- Bug in segmented control
Bug in segmented control
hi all
i have this error when i press back and inthe previuos activity i have your controll.
it is not the first time i advise you about a bug with this exception in other controlls.
version 17.4.0.39
not always but often
thanks
ps tried also version 40 and 41 but is the same.
android.runtime.JavaProxyThrowable: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Android.Graphics.Paint'.
at Java.Interop.JniPeerMembers.AssertSelf (Java.Interop.IJavaPeerable self) [0x00029] in :0
at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeVirtualVoidMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x00000] in :0
at Android.Graphics.Paint.set_Color (Android.Graphics.Color value) [0x00028] in <82e50ec67af648c3b9f43b3d70e21b96>:0
at Syncfusion.Android.Buttons.SelectionStrip.OnDraw (Android.Graphics.Canvas canvas) [0x00124] in <502a6d9fdcb4498795124beb60b29d63>:0
at Android.Views.View.n_OnDraw_Landroid_graphics_Canvas_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_canvas) [0x00011] in <82e50ec67af648c3b9f43b3d70e21b96>:0
at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.22(intptr,intptr,intptr)
--- End of stack trace from previous location where exception was thrown ---
at Java.Interop.JniEnvironment+InstanceMethods.CallNonvirtualBooleanMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x0008e] in :0
at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeVirtualBooleanMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x0005d] in :0
at Android.Views.ViewGroup.DrawChild (Android.Graphics.Canvas canvas, Android.Views.View child, System.Int64 drawingTime) [0x00069] in <82e50ec67af648c3b9f43b3d70e21b96>:0
at Syncfusion.Android.Buttons.ContainerLayout.DrawChild (Android.Graphics.Canvas canvas, Android.Views.View child, System.Int64 drawingTime) [0x00113] in <502a6d9fdcb4498795124beb60b
SIGN IN To post a reply.
5 Replies
LU
Luca
January 14, 2020 08:56 AM UTC
this bug is critical.
thanks
HM
Hemalatha Marikumar
Syncfusion Team
January 14, 2020 11:56 AM UTC
Hi Alberto,
Greetings from Syncfusion.
We have tried to reproduce the reported issue with provided stack trace and its working fine at our end. However, we have fixed the reported issue “Object disposed exception thrown in SegmentedControl when navigating from activities” based on the provided call stack information and the patch for this fix can be downloaded from the following location.
Recommended approach - exe will perform automatic configuration
Please find the patch setup from below location:
(OR)
Advanced approach – use only if you have specific needs and can directly replace existing assemblies for your build environment
Please find the patch assemblies alone from below location:
(OR)
Nuget:
Note:
We have provided a patch for this issue in 17.4.0.39 version. Because we only provide patch for Main release and SP release version. We don’t have support to provide patch for weekly nugets and Beta release versions.
Disclaimer:
Please note that we have created this patch for version 17.4.0.39 specifically to resolve the following issue reported in the forum 150548.
If you have received other patches for the same version for other products, please apply all patches in the order received.
Note: Please clear the cache before using patch
Please let us know the provided patch resolve issue at your end?
Regards,
Hemalatha M.
HM
Hemalatha Marikumar
Syncfusion Team
January 29, 2020 04:59 AM UTC
Hi Alberto,
Can you please confirm whether or not your reported issue has been resolved by the provided fix?
Regards,
Hemalatha M.
LU
Luca
January 30, 2020 12:48 PM UTC
hi,
yes now it is working.
can i download last version? 17.0.4.46?
HM
Hemalatha Marikumar
Syncfusion Team
January 31, 2020 06:35 AM UTC
Hi Luca,
Thanks for your confirmation.
Since we have fixed this issue based on the stack trace, we are planning to move this fix after we get confirmation. Now, we are going to include this fix in our upcoming weekly Nuget release, which is expected to be released on February 11,2020.
Regards,
Hemalatha M.
SIGN IN To post a reply.
- 5 Replies
- 2 Participants
-
LU Luca
- Jan 10, 2020 03:51 PM UTC
- Jan 31, 2020 06:35 AM UTC