UnsatisfiedLinkError on startup about jda

[AjaxGb]

Jeez, thanks @kantenkugel. My bad.

[kantenkugel]

Here are a few things that are worth trying:

• Check if another version of JDA is running on the PC currently (The error says that the opus-file can not be used as another program blocks it).and try it with them closed.
• Try deleting the opus*.dll file before launching the bot
• Make sure that JDA is properly put inside of your Jar-file (open the .jar file with any gzip program an check if the opus directory exists as well as the net/dv8tion/jda one)

Please let us know, if you could find out anything new with the given suggestions.
I am also interested in how exactly you are including JDA into your project. gradle/maven, download from build-server or adding the JDA source?

[kantenkugel]

By the way: i wish you luck with receiving audio... we didn't test that at all yet (yes, there are packets incoming, but we didn't check if it is easy to use or to play back). Receiving audio is not even really alpha. We are still working on finalizing the sending part (for 1.3.0 release)

[kantenkugel]

And... oh wow... i didn't know that we are polluting the temp-folder with all those opus.dll files

[AjaxGb]

@kantenkugel

• There are no other versions of JDA running.
• I checked, the file seems to be deleted after the program crashes. In any case, I couldn't find any by the names given in the error message. Plenty of other opusXXXXX... files, though. Deleting them has no effect.
• The jar I'm working with now looks like this.

I've tried the first two of those methods. Haven't tried compiling from source.

[kantenkugel]

No, you should not compile from source :) I was just asking to know if you did, cuz that could be a cause of error.
I am really confused, on why this happens... Each instance of JDA should create its own dll-file in the temp-folder to load as library. The docs of the used methods tell us that that file is unique... and we only access it once to load it.

So somehow JDA locks itself out from the created temp-file (the code closes the output-stream to the file, but maybe it's not free again)... It is either that (we are still using it somehow before the read-attempt), or the .jar-file somehow loses permissions for the file. We will have to test this problem a little bit. This did not occur for anyone else yet, so it's gonna be hard to figure out.

If you find out anything new before we do, please let us know.
Also feel free to join our channel in the Discord API Guild (invite in README-file), to have a better chat

[DV8FromTheWorld]

@AjaxGb JDA v1.3.0 has been released. Please try it and see if this problem still exists.
https://github.com/DV8FromTheWorld/JDA/releases/tag/v1.3.0

[AjaxGb]

Yeah, it's working now! Thanks!