React Native 0.81.1 android error "Nitro runtime not installed yet"

[jhkette]

Hi,
Looking for help
I am using:
"react-native": "0.81.1",
"react-native-iap": "^14.5.0",
"react-native-nitro-modules": "^0.31.10"

node: 20.19.6
and Java 17

I am simply installing the react-native-iap and react native nitro modules and using the setup in the recent documentation. This works totally fine in ios. However, it isn't working on android (both emulator and physical device) and i cannot connect to the play store to get purchases/subscriptions. I'm getting this specific error.

[react-native-iap]: PurchaseError
Nitro runtime not installed yet. Ensure react-native-nitro-modules is initialized before calling IAP.

I initialise react-native-iap as in the docs very much like this:

const {connected, products, subscriptions, fetchProducts, requestPurchase} =
useIAP({
onPurchaseSuccess: (purchase) => {
console.log('Purchase successful:', purchase);
handleSuccessfulPurchase(purchase);
},
onPurchaseError: (error) => {
console.error('Purchase failed:', error);
handlePurchaseError(error);
},
});

Then i fetch products. I have left the native android files - i.e, I have briefly tried to initalise react-native-nitro-modules in the MainApplication.kt file - but removed it - as it wasn't helping. I also tried importing react-native-nitro-modules in the index.js file of my react-native project - but removed as it didn't help. Is there something I am doing wrong? Help would be appreciated.

[hyochan]

Hi @jhkette,

Thanks for reporting this issue! The "Nitro runtime not installed yet" error occurs when the JSI runtime isn't properly initialized before the IAP module tries to create its HybridObject.

Recommended Steps

1. Upgrade to the latest version

First, please upgrade to the latest version of react-native-iap:

npm install react-native-iap@latest
# or
yarn add react-native-iap@latest

Current latest version is 14.7.0.

2. Clean build and reinstall

Android builds can sometimes cache stale native code. Try a complete clean:

# Clean Android build
cd android
./gradlew clean
cd ..

# Remove node_modules and reinstall
rm -rf node_modules
npm install  # or yarn install

# Rebuild
npx react-native run-android

3. Verify Nitro autolinking

When building, check your Android build logs for this message:

[NitroModules] 🔥 NitroIap is boosted by nitro!

If you don't see this message, the Nitro autolinking may not be working correctly.

4. Check your Metro bundler

Make sure Metro is running fresh:

npx react-native start --reset-cache

5. Verify dependencies

Ensure your react-native-nitro-modules version is compatible:

{
  "dependencies": {
    "react-native-iap": "^14.7.0",
    "react-native-nitro-modules": "^0.31.1"
  }
}

Additional Debugging

Could you please provide:

1. The full error stack trace from the Android logs (adb logcat)
2. Your android/build.gradle and android/app/build.gradle files
3. Output of npx react-native info

Note on iOS working but Android not

This is a common pattern when the native module linking is incomplete on Android. The iOS and Android native setups are independent, so one can work while the other fails.

Let me know if these steps help resolve the issue!

[jhkette]

Thanks @hyochan for getting back to me! I have tried a couple of your suggestions. But will get back to you if resolved or with more details (build.gradle files/ adb logcat error logs, npx react-native info output) this week if i still have problems.

[jhkette]

Hi @hyochan

react-native-info.txt

(the authentication stuff is obviously a log to do with something else)

Hi,
I now have

"react-native-nitro-modules": "^0.31.10",
"react-native-iap": "^14.7.0",
"react-native": "0.81.1",

I am still having the same issue - here is the info listed above. The app/build.gradle file i am adding google billing dependency and this
"io.github.hyochan.openiap:openiap-google:1.3.21" . Some of the app/build.gradle was set up by someone else and i find the React Native documentation on it not the best but .. i think it is ok..

For info I am essentially updating a project. On a prior version of the project we got stuck on RN 0.70 or something and we were using an older (pre nitro modules) version of rn-iap and it works fine. Its not that much of an emergency but it would be nice to get the project updated. With the adb logcat output - i tried to narrow it down as much as i could - the authentication stuff is a console log from something else as i'm sure you will guess. I was thinking maybe i should try upgrading react-native.

The one error (paraphrased) that does maybe? seem significant on the adb logs is "Nitro not ready yet. Listener inert until initConnection()".

Thanks for your help.

[hyochan]

Hi @jhkette,

Thanks for providing the detailed information! I found the issue.

The Problem

In your android/app/build.gradle, you have duplicate dependencies that conflict with react-native-iap:

dependencies {
    implementation("com.android.billingclient:billing:7.0.0")  // ❌ Remove this
    implementation("io.github.hyochan.openiap:openiap-google:1.3.21")  // ❌ Remove this
}

You should NOT add these manually. react-native-iap already includes openiap-google as a transitive dependency with the correct version. Adding them manually causes version conflicts and can break the Nitro module initialization.

Solution

1. Remove manual dependencies from android/app/build.gradle

Remove these lines from your dependencies block:

dependencies {
    implementation("com.facebook.react:react-android")
-   implementation("com.android.billingclient:billing:7.0.0")
-   implementation("io.github.hyochan.openiap:openiap-google:1.3.21")

    if (hermesEnabled.toBoolean()) {
        implementation("com.facebook.react:hermes-android")
    } else {
        implementation jscFlavor
    }
}

2. Clean and rebuild

cd android
./gradlew clean
cd ..

rm -rf node_modules
npm install

npx react-native run-android

3. Reset Metro cache

npx react-native start --reset-cache

Why This Happens

The react-native-iap library automatically manages its native dependencies through:

• openiap-versions.json - defines the correct OpenIAP version
• android/build.gradle - automatically includes the dependency

When you manually add conflicting versions, it can cause class loading issues that prevent the Nitro HybridObject from being created properly.

Additional Notes

Your build logs show that Nitro is being configured correctly:

[NitroModules] 🔥 NitroIap is boosted by nitro!
[NitroModules] 🔥 Your app is boosted by nitro modules!

This confirms the issue is not with Nitro setup, but with dependency conflicts at runtime.

Let me know if removing those manual dependencies resolves the issue!

[jhkette]

Hi @hyochan
Ok thanks loads for your help. I think i may have added these when i started having problems - not sure anymore. I have removed them I i did a very thorough cache clean (cleared the whole android build folder, cleared watchman cache, metro cache ran bash gradle clean) and I'm sorry but I still have an issue. I'm actually just working around it for the moment. It's more just to let you know as maintainers. This error is specific to android as mentioned - so I don't think it's anything to do with how i'm calling the react-native-iap library or anything - it's working perfectly in iOS! It maybe some kind of edge case of my setup I guess.

The above is from a physical device.
With all the same info as above (but with the dependencies removed from app/build.gradle).

As mentioned I'm moving on from the payment onto other parts of the project at the moment. I may have to work around it. Thanks for being so responsive anyway.

"@aws-amplify/react-native": "^1.2.0",
"@graphql-codegen/cli": "^6.0.0",
"@graphql-codegen/near-operation-file-preset": "^3.1.0",
"@hookform/resolvers": "^5.2.1",
"@react-native-async-storage/async-storage": "^2.2.0",
"@react-native-clipboard/clipboard": "^1.16.3",
"@react-native-community/netinfo": "^11.4.1",
"@react-native-vector-icons/evil-icons": "^12.3.0",
"@react-native-vector-icons/feather": "^12.3.0",
"@react-native-vector-icons/fontawesome6": "^12.2.0",
"@react-native/new-app-screen": "0.81.1",
"@react-navigation/bottom-tabs": "^7.4.7",
"@react-navigation/native": "^7.1.17",
"@react-navigation/native-stack": "^7.3.26",
"@reduxjs/toolkit": "^2.9.0",
"@sentry/react-native": "^6.22.0",
"aws-amplify": "^6.15.5",
"aws-appsync-subscription-link": "^3.1.3",
"date-fns": "^4.1.0",
"i18next": "^25.5.2",
"libphonenumber-js": "^1.12.17",
"lottie-react-native": "^7.3.4",
"mixpanel-react-native": "^3.1.2",
"react": "19.1.0",
"react-hook-form": "^7.62.0",
"react-i18next": "^15.7.3",
"react-native": "0.81.1",
"react-native-bootsplash": "^6.3.10",
"react-native-calendars": "^1.1313.0",
"react-native-chart-kit": "^6.12.0",
"react-native-crypto-js": "^1.0.0",
"react-native-dropdown-select-list": "^2.0.5",
"react-native-encrypted-storage": "^4.0.3",
"react-native-exception-handler": "^2.10.10",
"react-native-gesture-handler": "^2.28.0",
"react-native-get-random-values": "^1.11.0",
"react-native-iap": "^14.7.0",
"react-native-keychain": "^10.0.0",
"react-native-nitro-modules": "^0.31.10",
"react-native-paper": "^5.14.5",
"react-native-paper-dates": "^0.22.50",
"react-native-reanimated": "^4.2.0",
"react-native-safe-area-context": "^5.6.1",
"react-native-screens": "^4.16.0",
"react-native-simple-gauge": "^0.3.1",
"react-native-svg": "^15.13.0",
"react-native-tracking-transparency": "^0.1.2",
"react-native-vector-icons": "^10.3.0",
"react-native-version-check": "^3.5.0",
"react-native-webview": "^13.16.0",
"react-native-worklets": "^0.7.1",
"react-redux": "^9.2.0",
"yup": "^1.7.0",
"yup-phone": "^1.3.2"

These are my dependencies. Just FYI.

[hyochan]

Hi @jhkette,

Thanks for the detailed follow-up. The build logs showing [NitroModules] 🔥 NitroIap is boosted by nitro! confirm that autolinking is working correctly, so this appears to be a runtime initialization timing issue rather than a build configuration problem.

To help diagnose further, could you provide:

1. Full stack trace - When the error occurs, can you capture the complete Java/Kotlin stack trace from adb logcat? Specifically:

   adb logcat -s ReactNativeJS:V AndroidRuntime:E

2. Initialization timing - Where exactly do you call useIAP or initConnection? Is it in the root component or a nested screen?

3. Minimal reproduction - If possible, could you create a minimal repo that reproduces the issue? This would help us isolate whether it's a library issue or an interaction with other dependencies in your project (I notice you have quite a few native modules like AWS Amplify, Sentry, Reanimated, etc.).

4. Quick test - Could you try wrapping your IAP initialization with a small delay to see if it's purely a timing issue?

   useEffect(() => {
     const timer = setTimeout(async () => {
       try {
         await initConnection();
       } catch (e) {
         console.log('IAP init error', e);
       }
     }, 1000);
     return () => clearTimeout(timer);
   }, []);

This will help us determine whether the issue is with Nitro's initialization timing or something else specific to your setup.

[jhkette]

Hi @hyochan - Thanks again - all very good suggestions. I will try and get back to you this week or by early next week with these. A minimal reproduction is a good idea. It maybe early next week - hope that is ok! I am calling useIAP in a react context file - this is used to fetch subscriptions - then the provider wraps around the main app component. This is how prior developer set it up. However, from my recollection - I have tried to change it once and just added it to a screen and it still happened. I'll get back with more detailed info as soon as possible.