-
Notifications
You must be signed in to change notification settings - Fork 508
Cannot load 'System.Security.Cryptography.Native.Apple' after recent CoreRT upgrade #8241
Comments
#33236 added It can be worked around by changing this: https://github.com/dotnet/corert/blob/master/src/ILCompiler/src/ConfigurablePInvokePolicy.cs#L73 to check for both |
Thank you, Jan. What would be the proper fix / should I log a bug in dotnet/runtime? (We prefer running our production builds on CoreRT master without branching if at all possible). |
I have submitted dotnet/runtime#39717 to fix it in dotnet/runtime. It will take a while until we can pick up that fix (we need to do the runtimelab migration first). If you would like to have the workaround checked, feel free to submit PR once you verify that it works. |
Keep this open to track removing the workaround. |
Thank you so much for the quick help, Jan. We have our app running on Rosetta 2 / Big Sur ARM now, almost flawlessly :) |
Fixed by dotnet/runtimelab#98 |
Hi all,
Has something been changed to the build system recently that means there's a chance the native parts of
System.Security.Cryptography.Native.Apple
don't get properly statically linked with the binary anymore?Since our recent update to latest CoreRT, I get this when using any crypto functions:
System.DllNotFoundException: Unable to load DLL 'System.Security.Cryptography.Native.Apple': The specified module could not be found.
The text was updated successfully, but these errors were encountered: