-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
[Android] Unable to auto-initialise connection #2836
Comments
I added errorCallback where this can be retried. |
Thanks for the update but I don't how this is helping for this issue. |
We decided to patch the lib and rollback the changes that have been applied here on eventEmitter.ts : bdfd9f4 It seems that this fix generated more issues than it resolved. index 5aaf51b..f5ae652 100644
--- a/node_modules/react-native-iap/src/eventEmitter.ts
+++ b/node_modules/react-native-iap/src/eventEmitter.ts
@@ -59,17 +59,17 @@ export const purchaseUpdatedListener = (
proxyListener,
);
- if (isAndroid) {
- getAndroidModule()
- .startListening()
- .catch((error: unknown) => {
- if (errorCallback) {
- errorCallback(error);
- } else {
- throw error;
- }
- });
- }
+ // if (isAndroid) {
+ // getAndroidModule()
+ // .startListening()
+ // .catch((error: unknown) => {
+ // if (errorCallback) {
+ // errorCallback(error);
+ // } else {
+ // throw error;
+ // }
+ // });
+ // }
return emitterSubscription;
}; |
Description
I know an issue have already been opened and closed for this issue but it seems the lastest versions of the lib have increased the occurence of it. From rare to often
We upgraded the lib version from 12.10.7 to 12.15.2, without changing our code and this issue is happening from 1 time in a week, to 100 times in a week.
Environment:
To Reproduce
[Optional] Additional Context
It seems that users can still be able to get subscriptions after some tries or later.
The text was updated successfully, but these errors were encountered: