Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Billing is unavailable. This may be a problem with your device, or the Play Store may be down. #2795

Open
MariusCatanoiu opened this issue Jul 3, 2024 · 3 comments

Comments

@MariusCatanoiu
Copy link

Hello. I get this error after upgrading from 12.10.4 to 12.15.1

Environment:

  • react-native-iap: 12.15.1
  • react-native: 0.72.5
  • Platforms (iOS, Android, emulator, simulator, device): android, multiple real devices
Error Billing is unavailable. This may be a problem with your device, or the Play Store may be down. 
    node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:105:59 promiseMethodWrapper
    node_modules/react-native-iap/src/eventEmitter.ts:62:37 purchaseUpdatedListener
    src/screens/main/RemotePurchaseModule.tsx:90:59 ?anon_0_
    (native) throw
    node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:23 asyncGeneratorStep
    node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:26 _throw
    /root/react-native/packages/react-native/ReactAndroid/hermes-engine/.cxx/MinSizeRel/1x3k484k/arm64-v8a/lib/InternalBytecode/InternalBytecode.js:53:16 tryCallOne
    /root/react-native/packages/react-native/ReactAndroid/hermes-engine/.cxx/MinSizeRel/1x3k484k/arm64-v8a/lib/InternalBytecode/InternalBytecode.js:139:27 anonymous
    (native) apply
    node_modules/react-native/Libraries/Core/Timers/JSTimers.js:247:22 anonymous
    node_modules/react-native/Libraries/Core/Timers/JSTimers.js:111:14 _callTimer
    node_modules/react-native/Libraries/Core/Timers/JSTimers.js:161:14 _callReactNativeMicrotasksPass
    node_modules/react-native/Libraries/Core/Timers/JSTimers.js:415:41 callReactNativeMicrotasks
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:392:41 __callReactNativeMicrotasks
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:132:38 anonymous
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:368:10 __guard
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:131:16 flushedQueue
    node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:127:28 invokeCallbackAndReturnFlushedQueue
@MariusCatanoiu
Copy link
Author

I work withcom.google.gms:google-services:4.4.2, targetSdkVersion and compileSdkVersion 34

@MoritzCooks
Copy link

MoritzCooks commented Aug 26, 2024

I face this issue once we uploaded the Android version to PlayStore review. One of the device names that triggers that error is called sdk_goog3_gpc_x86_64 which immediately appears after upload of the new version without the version being available through any track yet. So this has to be a Google bot which is installing and testing the app.

In addition I faced this issue once locally on my device that was not signed in Google PlayStore.

Hope this helps!

@Moi6AP
Copy link

Moi6AP commented Sep 14, 2024

Any solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants