Felix Barz

Okay. I think I will still leave this issue open, as it might be relevant for others as well.

Thank you for the PR. I will try to review it within the next few days!

Hi @f-person. I wanted to ask if you need any help with the PR?

@rhbrunetto No, I am currently not actively working on it. Feel free to continue the PR!

Generally speaking: Yes, use the FFI-API directly is the way to go. You also do not have to extend the library for that. You can directly instanciate a `LibSodiumFFI` simply...

Oh okay, that is a problem. Maybe you should open an issue over there to see if they can enable it? I guess they leave it out by default for...

And regarding the freezed files: Yes, that is correct. The generated files are not checked in on purpose, thus the package is not usabled directly from git. Creating a seperate...

This might have to do with how the native binaries are compiled. Generally, libsodium only includes AES for compatibility reasons, but does not "actively" support it. So I guess you...

> Right, so it's not that easy. It seems that: `swift-sodium` doesn't support AES-GCM. https://github.com/jedisct1/swift-sodium > > ``` > Invalid argument(s): Failed to lookup symbol 'crypto_aead_aes256gcm_abytes': dlsym(RTLD_DEFAULT, crypto_aead_aes256gcm_abytes): symbol not...

No, I don't think so - the android build hasn't really changed. However, there problem there is not missing symbols, but some low level error. I already compile with all...