🔧 [Runtime not ready]: Error: Exception in HostFunction: dlopen failed: library 'libcrypto.so' not found

[joanscure]

How were you trying to build the app?

The app crashes at runtime with a dlopen failed error when trying to load libcrypto.so. The error occurs in the libreactnativequickcrypto.so library within the clns-7 namespace.

Android Project

buildscript {
    ext {
        buildToolsVersion = "36.0.0"
        minSdkVersion = 24
        compileSdkVersion = 36
        targetSdkVersion = 36
        ndkVersion = "27.1.12297006"
        kotlinVersion = "2.1.20"
    }
...
}

Error Details

[runtime not ready]: Error: Exception in HostFunction: dlopen failed: library 'libcrypto.so' not found: needed by /data/app/~~ljd-mG63b8rfq4CAjDvLLR9A==/com.lockWallet~xpg-Ko6T-KuH_lsjzVbGFPDAGVA==/base.apk!/lib/arm64-v8a/libreactnativequickcrypto.so in namespace clns-7

Stack Trace

anonymous@195766:42
loadModuleImplementation@275:13
guardedLoadModule@182:37
metroRequire@96:91
anonymous@193173:32
loadModuleImplementation@275:13
guardedLoadModule@182:37
metroRequire@96:91
anonymous@193101:50
loadModuleImplementation@275:13
guardedLoadModule@182:37
metroRequire@96:91
anonymous@1303:17
loadModuleImplementation@275:13
guardedLoadModule@175:46
metroRequire@96:91
global@209168:3

Steps to Reproduce

1. Set up React Native project with react-native-quick-crypto
2. Compile on Windows for Android target
3. Install and run the app on Android device
4. App crashes with the dlopen error

Full build logs

## Full Build Logs
The complete build logs are too long for GitHub issues. You can find them here:
https://gist.github.com/joanscure/a92c9cd60419f2a2e36be3f1f6338ea4

Project dependencies

"dependencies": {
    "@dr.pogodin/react-native-fs": "^2.35.1",
    "@gorhom/bottom-sheet": "5",
    "@react-native-clipboard/clipboard": "^1.16.3",
    "@react-native-community/netinfo": "^11.4.1",
    "@react-native-firebase/app": "^23.1.0",
    "@react-native-firebase/auth": "^23.1.0",
    "@react-native-firebase/firestore": "^23.1.0",
    "@react-native-firebase/functions": "^23.1.0",
    "@react-native-vector-icons/ionicons": "^12.3.0",
    "@react-native/new-app-screen": "0.81.0",
    "@react-navigation/drawer": "^7.5.7",
    "@react-navigation/native": "^7.1.17",
    "@react-navigation/native-stack": "^7.3.25",
    "@react-navigation/stack": "^7.4.7",
    "lodash": "^4.17.21",
    "lottie-react-native": "^7.3.2",
    "react": "19.1.0",
    "react-native": "0.81.0",
    "react-native-bootsplash": "^6.3.10",
    "react-native-device-info": "^14.0.4",
    "react-native-edge-to-edge": "^1.6.2",
    "react-native-gesture-handler": "^2.28.0",
    "react-native-keyboard-manager": "^6.5.16-0",
    "react-native-mmkv": "latest",
    "react-native-modal": "^14.0.0-rc.1",
    "react-native-nitro-modules": "^0.28.1",
    "react-native-nitro-sqlite": "^9.1.11",
    "react-native-quick-crypto": "^0.7.17",
    "react-native-reanimated": "^3.15.5",
    "react-native-safe-area-context": "^5.6.0",
    "react-native-screens": "^4.14.1",
    "react-native-securerandom": "^1.0.1",
    "react-native-size-matters": "^0.4.2"
  },

QuickCrypto Version

0.7.17

Target platforms

Android

Operating system

Windows

Can you build the QuickCrypto Example app?

I didn't try (⚠️ your issue might get ignored & closed if you don't try this)

Additional information

• I am using Expo
• I have read the Troubleshooting Guide
• I agree to follow this project's Code of Conduct
• I searched for similar issues in this repository and found none.

[joanscure]

I was able to fix this issue by manually adding the OpenSSL native libraries.
For some reason, the libcrypto.so and libssl.so files from the io.github.ronickg:openssl dependency are not being packaged into the APK.
Once I extracted them from the AAR and placed them under app/src/main/jniLibs/arm64-v8a/ (and the other ABIs), the error went away.

It seems that the OpenSSL libraries are included in the dependency, but they are not automatically merged into the build output. That’s why libreactnativequickcrypto.so couldn’t find libcrypto.so at runtime.

Could the team investigate why these libraries are not being merged automatically during the build process? It seems like the dependency includes them, but they don’t end up in the final APK.