-
Notifications
You must be signed in to change notification settings - Fork 316
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
The completion block is not working when downgrade plan #3020
Comments
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out! |
Thanks for the report! I'm looking into this right now.
There's a few things missing in your report, please provide these plus a few follow-up questions:
|
Also any chance you removed some logs? Looks like you have |
I was looking into #3020, and saw that we already have this test to cover downgrades. I added an extra assertion to verify entitlements. I also ran this test on iOS 17 and it passes.
Looking into #3020, it would have been helpful to see these.
… downgrades Fixes #3020. This essentially reverts #2890. As shown in #3020, downgrades are reported with the same transaction identifier as the original transaction. Therefore our approach in #2890 is invalid. We considered checking whether the `SKPayment` in the `SKPaymentTransaction` matches the one added to the queue as a way to disambiguate these transactions, but it doesn't. So we have no way of telling the difference between queue transactions and purchases. I've left the original tests as a way to at least document this behavior.
Thanks again for the report. We've identified the issue thanks to your logs, and are preparing a new release with the fix. |
Looking into #3020, it would have been helpful to see these.
… downgrades (#3028) Fixes #3020. This essentially reverts #2890. As shown in #3020, downgrades are reported with the same transaction identifier as the original transaction. Therefore our approach in #2890 is invalid. We considered checking whether the `SKPayment` in the `SKPaymentTransaction` matches the one added to the queue as a way to disambiguate these transactions, but it doesn't. So we have no way of telling the difference between queue transactions and purchases. I've left the original tests as a way to at least document this behavior.
This issue has been automatically locked due to no recent activity after it was closed. Please open a new issue for related reports. |
… downgrades (#3028) Fixes #3020. This essentially reverts #2890. As shown in #3020, downgrades are reported with the same transaction identifier as the original transaction. Therefore our approach in #2890 is invalid. We considered checking whether the `SKPayment` in the `SKPaymentTransaction` matches the one added to the queue as a way to disambiguate these transactions, but it doesn't. So we have no way of telling the difference between queue transactions and purchases. I've left the original tests as a way to at least document this behavior.
Describe the bug
A clear and concise description of what the bug is. The more detail you can provide the faster our team will be able to triage and resolve the issue. Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.
Additional context
The text was updated successfully, but these errors were encountered: