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.

Sign up for GitHub

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

Jump to bottom

SfBusyIndicator v20.1.0.50+ causes MemoryAccessViolation Exception on UWP #48

Open
SunshineSpring666 opened this issue May 6, 2022 · 1 comment
Open

SfBusyIndicator v20.1.0.50+ causes MemoryAccessViolation Exception on UWP #48

SunshineSpring666 opened this issue May 6, 2022 · 1 comment

Comments

@SunshineSpring666
Copy link

Hi Syncfusion Team,
Starting from Xamarin SfBusyIndicator v20.1.0.50, when setting Current.MainPage on an Xamarin.Forms UWP app, MemoryAccessViolation is thrown with no stack traces shown. Xamarin SfBusyIndicator v20.1.0.48 works just fine. Thanks.
Best Regards
@RubaShanmugamm
Copy link

Hi SunshineSpring,

Sorry for the inconvenience.

We are able to reproduce the reported issue. We have fixed the reported issue and the fix will be included in our upcoming SP1 release which is expected to be rolled out on May 11, 2022. We appreciate your patience until then.

Regards,
Ruba Shanmugam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SunshineSpring666 @RubaShanmugamm