You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PlatformException(400, The product id <our redacted, correct product id> provided doesnt match with any product in the receipt., Chargebee error, null)
The id in the error message is definitely correct and exists.
purchase sometimes fails for some users.We're using the flutter sdk:
The product id is definitely correct.
It currently affects a single user, who tried to purchase 7 times but it failed each time.
Perhaps the user picked a plan (say for 12 months) in the app & switched to a different plan in the purchase dialog? Then the receipt from Apple wouldn't match the expected product id.
The text was updated successfully, but these errors were encountered:
Perhaps the user picked a plan (say for 12 months) in the app & switched to a different plan in the purchase dialog? Then the receipt from Apple wouldn't match the expected product id.
This might result in a similar error. However I am not sure if the user would be able to switch the products? Is this something you have observed?
Also is there any differentiation among these products?(Like are they all Subscriptions/InAppPurchases?)
Switching the product in the purchase dialog isn't possible. I think I checked this at some point. The user can still switch through the Appstore later though.
All products are subscriptions, only differentiation is id, name, price and billing interval.
The id in the error message is definitely correct and exists.
purchase sometimes fails for some users.We're using the flutter sdk:
The product id is definitely correct.
It currently affects a single user, who tried to purchase 7 times but it failed each time.
Perhaps the user picked a plan (say for 12 months) in the app & switched to a different plan in the purchase dialog? Then the receipt from Apple wouldn't match the expected product id.
The text was updated successfully, but these errors were encountered: