-
Notifications
You must be signed in to change notification settings - Fork 540
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
[BUG] .NET9 SkiaSharp.Views.Blazor my app won't start #3068
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
I also tried Unhandled Exception:
System.DllNotFoundException: libSkiaSharp
at SkiaSharp.SKData..cctor() |
.NET9 I encountered this problem:Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] |
I also have this issue using 3.116.0-preview.6.1 var imageInfo = new SKImageInfo(...)
|
This is quite a serious issue for us too as we couldn't get 2.88.9 or 3.118.0-preview.1.2 working in .NET 9 using Blazor WASM. |
I don't know if it's related, but fo-dicom has some issues with loading plugins because .NET 9 has issues figuring out which architecture the CPU is. I don't know any more details -- but perhaps that's what's happening here as well as the dll can't be loaded. It would be good to be able to upgrade to .NET 9 for sure. |
Description
After upgrading my previously working .NET 8 app to .NET 9 using Blazor WASM, it fails to run in both Debug/Release builds.
Code
Expected Behavior
App should start.
Actual Behavior
App fails to start due to unhandled exception:
System.DllNotFoundException: libSkiaSharp
at SkiaSharp.SKData..cctor()
The page loading progress bar stays stuck at 100% and my Page won't load at all.
Version of SkiaSharp
2.88.9 (Current)
Last Known Good Version of SkiaSharp
Other (Please indicate in the description)
IDE / Editor
Visual Studio (Windows)
Platform / Operating System
Windows
Platform / Operating System Version
Windows/Browser
Devices
No response
Relevant Screenshots
No response
Relevant Log Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: