Synching of purchases despite observer-mode and disabling autoSyncPurchases
Maradox opened this issue · 4 comments
- I have updated Purchases SDK to the latest version
- I have read the Contribution Guidelines
- I have searched the Community
- I have read docs.revenuecat.com
- I have searched for existing Github issues
Describe the bug
We use RevenueCat in observerMode and set autoSyncPurchases to false. We don't call syncPurchases(). For purchasing a product the billing-library is used.
Though when purchasing a product, revenuecat updates the customerInfo object and the purchase is also shown on the website.
The documentation for autoSyncPurchases states:
Disable or enable syncing purchases automatically. If this is disabled, RevenueCat will not sync any purchase automatically, and you will have to call syncPurchases whenever a new purchase is completed in order to send it to the RevenueCat's backend. Auto syncing of purchases is enabled by default.
The documentation for Observer-Mode states:
On Android with Google Play (including cross-platform SDKs running on Android), any time a purchase or restore occurs in your app you should call the syncPurchases method to record it in RevenueCat. Failure to do so will result in no purchases being recorded.
We don't want RevenueCat to pickup these purchases, but despite setting .observerMode(true) and .dangerousSettings(DangerousSettings(autoSyncPurchases = false)) and not calling syncPurchases RevenueCat still syncs purchases.
- Environment
- Platform: Android
- SDK version: 5.7.1
- OS version: Likely affects all Android versions
- Android Studio version: Dolphin
- How widespread is the issue. Percentage of devices affected. happened on all three devices I tested this on
- Debug logs that reproduce the issue
After purchasing via billing-library:
processPurchase with Purchase. Json: ....
query purchases
queryPurchases result: ....
Additional context
We use observerMode since RevenueCat otherwise automatically consumes purchases, which we don't want.
We disable autoSyncPurchases since we want to use RevenueCat only for logged-in users and want to handle logged-out users ourselves.
Just letting you know the team is looking into this, we will update you with our findings
Hi, would you be able to provide full debug logs of the entire app lifecycle? Additionally, could you let me know how you are handling logged-out users in terms of configuring our SDK?