You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 2.1.1, the main change here is the inclusion of native code builds for Wasm that are compatible with .NET 7, because a specific version of emscripten is required. This work happened in #505.
The 2.1.2 release is also intended to fix a problem which was introduced in 2.1.1. Basically, from what I can tell, 2.1.1 is broken on net6.0-ios. This was reported at #516. The problem was introduced by the change to fix #506, and that change looked fine in principle, but it apparently triggers a bug in Mono's AOT code. That issue has been logged at dotnet/runtime#75700.
For the short term, since #506 was actually Windows-specific anyway, I have re-done that code change to take effect only for Windows builds. That change is commit 9adcbfc.
I have just published 2.1.2-pre20220916165053 up to nuget, so we can verify things. As soon as it looks okay, unless some other regression shows up, I will release 2.1.2.
A 2.1.2 release is imminent (any day now).
Since 2.1.1, the main change here is the inclusion of native code builds for Wasm that are compatible with .NET 7, because a specific version of emscripten is required. This work happened in #505.
The 2.1.2 release is also intended to fix a problem which was introduced in 2.1.1. Basically, from what I can tell, 2.1.1 is broken on net6.0-ios. This was reported at #516. The problem was introduced by the change to fix #506, and that change looked fine in principle, but it apparently triggers a bug in Mono's AOT code. That issue has been logged at dotnet/runtime#75700.
For the short term, since #506 was actually Windows-specific anyway, I have re-done that code change to take effect only for Windows builds. That change is commit 9adcbfc.
I have just published 2.1.2-pre20220916165053 up to nuget, so we can verify things. As soon as it looks okay, unless some other regression shows up, I will release 2.1.2.
FYI cc to @filipnavara @bricelam @ajcvickers
The text was updated successfully, but these errors were encountered: