Skip to main content

I'm having a problem with Android users, they purchase the subscription, but does not receive the subscription, instead they are asked to open the App to confirm the subscription

React Native
react-native-purchases: 4.5.2

I think this could have to do with requirements set by the customers’ bank or credit card - there wouldn’t be you could do on your end to change the Play Store payment flow. 


But when the user opens the App clicking on the link, should i have some listener or do something to process it?

The only thing i could find was https://docs.revenuecat.com/docs/observer-mode#2-sync-purchases-with-revenuecat-android-only but even putting it on the main screen it does not process the subscription


There is a listener you could plug into that would pick up any updates happening on the device: https://docs.revenuecat.com/docs/getting-started#optional-listening-for-customerinfo-update. Does that fire after the confirmation flow? 


I noticed i was using the old DSN, updated to the new public key system but i got the same result, also i noticed the webhook is not receiving any events.

 

I found this reference, but i assume you are doing this automatically? 

 

https://developer.android.com/google/play/billing/integrate#pending


I'm not sure how can i test the event you send because in order to test the subscription, i need to send a new version to the Play Store, so i don’t have access to console.log


Also, this happens with the test credit card too, so i think is not a problem between the bank and google


Ok, i was able to get the logs (you can install the App on your Android phone without uploading it to the play store and access the log), after confirming the purchase, its records:

```
[Error: There was a credentials issue. Check the underlying error for more details.]
````
Looking on stackoverflow, it seems to be a problem with the credentials between revenuecat and play store.

I had all the configuration done right, but the credentials where old (+6 month without using them), so I'm asumming they expired somehow, so i created new credentials and re-configured everything, i will update in 2 days.


Update: it worked, so if anyone faces this problem, i would recommend creating a new service account in gcp and updating it on revenuecat admin panel.


Reply