This file seems to randomly disappear causing build issues.

[khan-zia]

I might be missing something here and it might be an obvious reason, but so far it seems to be randomly loosing this file for Android at this location

".../node_modules/react-native-sodium/android/../libsodium/libsodium-android-i686/lib/libsodium.so".

The file is required inside react-native-sodium\android\CMakeLists.txt at the following copy operation

file(COPY ${PROJECT_SOURCE_DIR}/../libsodium/libsodium-android-${ARCH_DIR}/lib/libsodium.so DESTINATION "${PROJECT_SOURCE_DIR}/lib/${ANDROID_ABI}")

Please guide.

[khan-zia]

Update

@lyubo I have confirmed that the libsodium folder which gets unzipped from the precompiled gz, just magically disappears? any idea on why is that happening? It disappeared even after I manually extracted precompiled zip in there.

[tasn]

I'm experiencing the same. I'm not sure why it happens.
One "solution" would be to change the build step (when built as a dep) to just extract the tar if doesn't exist. Not sure what the correct solution is though.

[khan-zia]

Hopefully @lyubo will figure it out.

[lyubo]

Give me some context pls. (package version android SDK version, etc.). Have you tried example application. New version is alinged with the most recent react-native and is working just fine.

[tasn]

I'm not sure it's exactly what's going on, but it seems to fail after installing another package (I'm using the yarn package manager).

To reproduce:

1. Have a working project that builds correctly.
2. yarn add some-other-package

It fails.

Not sure if this is what's going on, but maybe a clue.

[khan-zia]

I am also using latest RN and SDK API 29. I don't have specific scenario either and I also use yarn. Every time it happens, I manually have to go to the folder and I extract the precompiled tar.

[lyubo]

Can you try with react-native-sodium@0.3.6 (i.e the version with gpg)?

[khan-zia]

Alright. I will try that version and if the issue persists, I will update here. However, I don't know when it will happen again since I am not sure how to reproduce it. I guess if it doesn't happen for quite a while, then we can assume that it works. Meanwhile, I will keep an eye for pin pointing the issue.

[tasn]

@lyubo, it's unrelated to that gpg change because it's about installing this package a dep, not building libsodium from source.

Do you also use yarn? Could you maybe try reproducing like I mentioned above?

[lyubo]

@tasn , last project I've used this library in used npm as package manager, so I can't tell if it is yarn related.

[khan-zia]

@tasn @lyubo , I have confirmed that this issue just happens right away after updating or adding with yarn. If you open the file browser and keep looking at it and run yarn command, the libsodium folder just disappears... This is very strange.

[tasn]

@tasn , last project I've used this library in used npm as package manager, so I can't tell if it is yarn related.

You can try reproducing it with npm too, the same way I and @khan-zia described.

[tbrent]

Having the same issue. No libsodium.so at the expected location in node_modules for any of the architectures. Unzipping the .tgz manually shows the contents as they should be. Using yarn as well.

[tbrent]

False alarm. Turns out Sublime was just not showing me .so files. The file is there, and it doesn't look like taking yarn actions does any damage to it. I am still facing an issue, but this is not it.

[tasn]

Just had it again on a new project... :|