-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
IOS: Downgrade subscription #2742
Comments
I encounter same issue. :( Before everything works fine. |
From my side. Only error get the error "react-native": "0.72.4", |
React Native: 0.67.4 Experiencing the same unknown error. In my case, trying to downgrade from an Annual duration sub to a monthly duration - within the same subscription group. This was working on our previous setup using [email protected] on StoreKit 1 |
Do anyone think this is the issue from Apple's sandbox env :D |
{"error": [Error: Purchased failed for sku:: Unable to Complete Request], "success": false} |
tried the below versions of the library:
React Native: 0.67.4 For the above, I am getting the same error message: [Error: Purchased failed for name_of_the_product: Unable to Complete Request] Only getting this with iOS, android seems to be working as expected. |
Description
Trying to downgrade a subscription is not working, but upgrading works fine.
Expected Behavior
Be able to upgrade and downgrade subscriptions.
Screenshots
Environment:
To Reproduce
Steps to reproduce the behavior:
Both subscriptions are in the same group, and have the same subscription duration of 1 month but they have different prices
While downgrading and passing to the requestSubscription promise the SKU for the cheaper subscription an error occurred which also triggered the purchaseErrorListener.
This is the error from the purcahseErrorListener:
[Optional] Additional Context
While debugging and inspecting my SANDBOX account, I noticed an interesting discrepancy: although the code caught an error during the subscription downgrade process, my account displays the subscription as active, despite the failure.
The text was updated successfully, but these errors were encountered: