-
Notifications
You must be signed in to change notification settings - Fork 699
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
[WASM] Bootstrap did not load app on mobile #13591
Comments
Thanks for the report. Can you indicate which platform you're using? Recent builds of .NET 8 enable SIMD by default, and some older browsers don't support that. You can check this table on the "Fixed-width SIMD" to determine the minimum version supported. |
I am using .NET 7, iOS 16.6.1 safari / chrome mobile 104.0.5112.99 Thanks! |
The issue looks like a memory corruption for arm64 specifically, and the location of the error changes on every build on the gallery. On desktop the app is working properly on x64, but not on arm64. The Url is never suppose to look that way:
Which would mean that the string is altered somehow, and cause this check to fail: uno/src/Uno.UI/UI/Xaml/ResourceResolver.cs Line 542 in 4c0adf8
|
Uno.Wasm.Bootstrap 8.0.0-dev.152 is OK . Has error when Uno.Wasm.Bootstrap >= 8.0.0-dev.192 |
This issue seems to have been addressed in recent Safari builds (both iOS and macOS arm64), closing for now. |
Current behavior
Uno.Wasm.Bootstrap version 8.0.0-dev.277
ExecutionMode : InterpreterAndAot
App did not load on mobile safari or mobile chrome. also noticed https://gallery.platform.uno/ did not load on mobile.
Uno.Wasm.Bootstrap version 8.0.0-dev.138 and before can load app correctly.
Expected behavior
Load wasm app on mobile correctly.
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
None
Environment
No response
NuGet package version(s)
No response
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: