DLL not found with standalone app but works fine in editor

Hello, I have sent you the project in the PM, please have a look.

 

I´m having the same problem DLLNotFoundException.

Unity: 2018.4.3f1
Scripting Runtime: 4.x
API Compatibility Level: 4.x

Im using a DLL to communicate over CAN with this adapter https://www.peak-system.com/PCAN-USB.199.0.html?&L=1

The dll does not work for both standalone and editor. Copying the dll to the project root will make it work in the editor and copying besides the .exe will make it work in standalone.

I have a project set up and can send it to you or file a bug report.

 

Filed a bug report (Case 1172323)

 

Response from QA:

I will test this once i get my hands on 2019.2

 

When your PC has a scanner connected to it and you run the project in editor and press space bar it will scan the document with the scanner and show you the scanned document in the unity image in the scene but when you make a standalone build and try to do the same the project just close it self when you press space bar. And the problem is it just straight up crashes and does not give you any error or any logs, while in editor it just works perfectly.


Here is the call stack when I attached the build with the Visual studio to get the logs.

 

Editor is fixed, standalone still not working

Tested with 2019.2.0b10

 

We are having a similar issue with SQLite.Interop.DLL.
We have our own managed library that refers to System.Data.SQLite.dll (which in turn has a dependency on the interop file)
Running in the editor is fine and everything works and logs correctly.
On build we receive the error

Fallback handler could not load library D:/snobal-xr/src/xr/unity/xr-app/Build/Snobal_Data/Mono/SQLite.Interop.dll
and a few other derivatives of this

The interop dll is found within build/myapp-data/plugins and there is no mono folder.
Both creating a mono folder manually and moving the dll, as well as copying the DLL to the root build folder worked.

We have the solution of writing a build script that will automatically do this task, however it is very hacky solution and I don't like it personally. It is not good for production.

Is there any new news on this issue?
Unity version 2019.1.11f1

 

I just got an email which stated:

It's now fixed in Unity 2019.2.2f1, 2019.3.0a12, 2020.1.0a1 and above.​

I did not test this though.

 

I have the exact same problem after upgrading to 2019.2.5f1. For some reason the dll's are being placed outside of the x86_64 folder in game_Date/Plugins folder:

No matter what import settings I choose or what folder in Plugins I put the libs in it just won't go into the x86_64 folder in the build causing the missing DLL errors. If I manually move them everything works fine. Any help?

 

@Tautvydas-Zilys



I've also tried putting into Plugins/x86_64 folder as well

 

@Tautvydas-Zilys thanks. I upgraded from 2018.3.11f1 to 2019.1.14f1 (briefly for like a day, can't remember if it was broke there) then to the current 2019.2.5f1

If you would like to clone the 2019.2.5f1 branch and have a look at it you can find it here: https://github.com/unitystation/unitystation/tree/mirrorprefabscenes

mirrorprefabscenes branch

 

This bug is pretty weird I couldn't reproduce it in clean project but I've finally found the issue.

DllImport (and prob P/Invoke) fails only when folder "x86_64" exists in Plugins folder (in build). I'm not sure but It may happen only in IL2CPP builds. What's weirder is that it started working after changing to Mono and than to il2cpp. To break it once again I had to restart Unity and delete Library folder.

Reproduce steps:
1. Make project
2. Add: https://github.com/discordapp/discord-rpc
3. Follow Unity setup for windows
4. Add the example dll usage class https://github.com/discordapp/disco...es/button-clicker/Assets/DiscordController.cs
5. Add this to any object on the scene
6. Build for x86_64 with IL2CPP
7. Make empty folder <project_name>_Data\Plugins\x86_64
8. Open game and check log file.

Or:
1. Get project from report bug 1185926
2. Continue from step 6. above


Workaround until fix:
1. Cut-Paste everything from "x86_64" to parent Plugin folder
2. Remove empty "x86_64" folder

 

Better fix:

These settings will put dll to the Plugins/x86_64 folder:


These settings will put dll to Plugins folder:


So check x86_x64 for every dll to prevent x86_64 folder from being created

 

Android Build working Perfectly when using Mono.
When using IL2CPP There is An Error In Android Device

DllNotFoundException: Unable to load DLL 'MonoPosixHelper': The specified module could not be found.

zipsharp.NativeZip.zipOpen2_32 (System.String pathname, System.Int32 append, System.IntPtr globalcomment, zipsharp.ZlibFileFuncDef32& pzlib_filefunc_def) (at <00000000000000000000000000000000>:0)
zipsharp.NativeZip.OpenArchive32 (zipsharp.ZlibFileFuncDef32 funcDef, zipsharp.Append append) (at <00000000000000000000000000000000>:0)
zipsharp.ZipArchive..ctor (System.IO.Stream stream, zipsharp.Append append, System.Boolean ownsStream) (at <00000000000000000000000000000000>:0)
System.IO.Packaging.ZipPackage.FlushCore () (at <00000000000000000000000000000000>:0)
System.IO.Packaging.Package.Flush () (at <00000000000000000000000000000000>:0)
System.IO.StreamWriter.Dispose (System.Boolean disposing) (at <00000000000000000000000000000000>:0)
System.IO.StreamWriter.Close () (at <00000000000000000000000000000000>:0)
System.Xml.XmlTextWriter.Close () (at <00000000000000000000000000000000>:0)
System.IO.Packaging.Package.WriteRelationships (System.Collections.Generic.Dictionary`2[TKey,TValue] relationships, System.IO.Stream stream) (at <00000000000000000000000000000000>:0)
System.IO.Packaging.Package.CreateRelationship (System.Uri targetUri, System.IO.Packaging.TargetMode targetMode, System.String relationshipType, System.String id, System.Boolean loading) (at <00000000000000000000000000000000>:0)
System.IO.Packaging.Package.CreateRelationship (System.Uri targetUri, System.IO.Packaging.TargetMode targetMode, System.String relationshipType) (at <00000000000000000000000000000000>:0)
DocumentFormat.OpenXml.Packaging.OpenXmlPackage.CreateRelationship (System.Uri targetUri, System.IO.Packaging.TargetMode targetMode, System.String relationshipType) (at <00000000000000000000000000000000>:0)
DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.AttachChild (DocumentFormat.OpenXml.Packaging.OpenXmlPart part, System.String rId) (at <00000000000000000000000000000000>:0)
DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.InitPart[T] (T newPart, System.String contentType, System.String id) (at <00000000000000000000000000000000>:0)
DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.InitPart[T] (T newPart, System.String contentType) (at <00000000000000000000000000000000>:0)
DocumentFormat.OpenXml.Packaging.WordprocessingDocument.AddMainDocumentPart () (at <00000000000000000000000000000000>:0)
DefaultNamespace.ResumeBuilder.Generate () (at <00000000000000000000000000000000>:0)
UnityEngine.Events.UnityEvent.Invoke () (at <00000000000000000000000000000000>:0)
UnityEngine.EventSystems.ExecuteEvents.Execute[T] (UnityEngine.GameObject target, UnityEngine.EventSystems.BaseEventData eventData, UnityEngine.EventSystems.ExecuteEvents+EventFunction`1[T1] functor) (at <00000000000000000000000000000000>:0)
UnityEngine.EventSystems.StandaloneInputModule.ProcessTouchPress (UnityEngine.EventSystems.PointerEventData pointerEvent, System.Boolean pressed, System.Boolean released) (at <00000000000000000000000000000000>:0)
UnityEngine.EventSystems.StandaloneInputModule.ProcessTouchEvents () (at <00000000000000000000000000000000>:0)
UnityEngine.EventSystems.StandaloneInputModule.Process () (at <00000000000000000000000000000000>:0)

 

I got response from Unity that the bug is fixed in 2020 and will be backported to 2019.3 but they don't know when

 

Thank you very much. It was very helpful.
I found the issue here.
https://issuetracker.unity3d.com/issues/dlls-are-misplaced-in-standalone-player

 

Hello, I believe I experience issue tightly related to this thread.

I'm developing a VR project for Standalone. I use the a number of third-party Dll plugins for Windows x64 platform. In Editor mode everything works great, but the built project does not work as it is expected. After I launch compiled app, it says that not all modules in third-party plugins are available. Also VR is launched in some default mode, when camera is configured in stereo mode. After I move files from [_data/Plugins] to [_data/Plugins/x86_64] (where my third-party libraries are stored) VR works good and I can see the scene through my VR kit. To make my third-party plugin see all its modules I have to copy my third-party plugins, located in [_data/Managed] to the location of my native Dll files [_data/Plugins/x86_64]. After these manipulations built project works like it used to in Editor mode.

Is there any solution for that except moving/copy-pasting workaround?

All third-party plugins are tightly dependent on each other.
From my code I use DllImport for native c++ Dll and reference another plugin from my own Dll (using types and classes declared inside).

Unity 2019.3.0f6

 

@Tautvydas-Zilys I am having the same issue, with ArrayFire. I built the project in development mode, and it is having trouble with it. Would you mind walking me through the steps to fix it? I am using Unity 2018.4.9f1. I can provide more information if needed. Thanks for all your help! I also am inexperienced with importing dlls to Unity, and I got them via Nuget in VS. The NN (what I am using array fire for) works in editor, but not stand alone.

 

First of all, thanks for a quick response. To sum up the issue-I have an NN in creatures, and creatures are forced to eat the first couple food they encounter. However, this isn't happening in the built stand alone, but in the editor. When I built the project as a development build I get the error- DllNotFoundException: af. The af is referring to the ArrayFire dll I was using, and ArrayFire is an important part of the NN. Since the Dll isn't working, neither will the NN.
Thanks!

 

DllNotFoundException: af, is the exact error. It does work in the editor. I'm not sure how to run it in 64 bit, but it doesn't work in 32 bit, and probably not 64 but. I am relatively new to unity GUI. I can script in C# with the Unity functions, but unfamiliar with project building, ect.
Thanks!

 

FYI, I am on a mac. Its not the best with C#, but it works. The af.dll does exist in my project, with no specific settings, just a dll. I am pretty inexperienced with dlls, but I am pretty sure it is just a file.

 

Unfortunately I am on 2018.4.9f1.

 

I do not recall downloading af.bundle, and I don't think it is in my project. I looked all over, and didn't see it, and it wasn't with the other dlls.

Thanks!

 

Oh, ok thanks. But wouldn't that mean that it wouldn't work in the editor? Plus, I think I downloaded the mac version. I could try re-downloading, but it is a pain to get dlls to Unity.
https://arrayfire.com/download/

Thanks!

 

I'll surf the web a little to try and find out whats going on.
Thanks!

 

I just downloaded 2019.4.0f1 and I am still getting a DLL Not found exception.
Was this bug fixed in that release ?

 

These settings does not put my .dll files to plugin folder and creates a x86_64 folder. I am using unity 2019.3.0 f6.
What can be the problem?

 

Update to unity 2019.4

 

I found the problem. One of lib's included in these DLL had some code that reference an MFC lib.
Even though, I was not using this function it gave me the DLL not found exception. I removed this lib and created
a new lib that had no MFC references and everything worked.

 

Hello everyone,

The same issue more or less here. I am using a dll and it plays fine when in the editor, but is not loaded when I build the game. The strange thing however is that it plays also fine when I make a development build with script debugging enabled. How should I approach the issue?

 

EDIT: OK, I found the reason I had this problem was that my machine and the plugin are x86_x64, but the build was set to be x86. This still runs on a 64-bit machine, but since the dll wasn't made for that, it couldn't be loaded.

 

the program can't start the file api-ms-win-ntuser-sysparams-l1-1-0.dll is missing. what now how to get rid of this error on my PC. I found the same file on this website <SNIP> and now I'm a bit confused about what to do, download the file or just reinstall the program once again, already did it once.