DllNotFoundException for Standalone build on MacOS
When doing a standalone build on MacOS with Unity 2021.3.22f1 LTS (Noesis version 3.2.1) of our project I get this in the application log when starting the game:
I assume I can copy the dylib to some folder but shouldn't it resolve that automatically? Thank you!
Code: Select all
DllNotFoundException: Noesis assembly:<unknown assembly> type:<unknown type> member:(null)
at (wrapper managed-to-native) Noesis.GUI.Noesis_DisableSocketInit()
at Noesis.GUI.DisableSocketInit () [0x00000] in <4a5a6102291743178f32591befad79e6>:0
at NoesisUnity.InitCore () [0x00000] in <4a5a6102291743178f32591befad79e6>:0
at NoesisXaml.RegisterDependencies () [0x00008] in <4a5a6102291743178f32591befad79e6>:0
at NoesisXaml.Load () [0x00000] in <4a5a6102291743178f32591befad79e6>:0
at NoesisView.LoadXaml (System.Boolean force) [0x00025] in <4a5a6102291743178f32591befad79e6>:0
at NoesisView.OnEnable () [0x00019] in <4a5a6102291743178f32591befad79e6>:0
Re: DllNotFoundException for Standalone build on MacOS
Yes, this should work automatically.
Are you able to reproduce this in a clean Unity project with Noesis imported and using one of our sample, like the HelloWorld?
Are you able to reproduce this in a clean Unity project with Noesis imported and using one of our sample, like the HelloWorld?
Re: DllNotFoundException for Standalone build on MacOS
Yes, just created a clean project in Unity 2021.3.22 (guess the patch level doesn't matter), imported the 3.2.1 Noesis package and also imported the button example which comes with that package. It works great in the editor but provokes the same error in a standalone build. I'm on a Macbook Pro Intel with Ventura 13.3.1
edit: attached the project
edit: attached the project
- Attachments
-
- noesis-test.zip
- (144.44 KiB) Downloaded 207 times
Re: DllNotFoundException for Standalone build on MacOS
Our native library is not properly tagged for Apple silicon. Could you please create a ticket for this? (I am also observing a crash at shutdown when using Development Builds with ARM)
For now, your workaround is selecting only "Intel 64-bit" in the Architecture combobox when building the standalone.
For now, your workaround is selecting only "Intel 64-bit" in the Architecture combobox when building the standalone.
Who is online
Users browsing this forum: Bing [Bot] and 2 guests