Hello,
About a month ago me and my team allocated a sprint to migrate the App Store Server Notifications service and the StoreKit library from v1 to v2.
Once the implementation was completed, we started testing using the sandbox environment (which was supposed to provide greater stability and maturity in v2).
The testing session went well, we managed to test various scenarios without noticing any issue (successful payment, failed payment, renewal etc).
This week, before doing the production deployment, a final testing session was scheduled.
Out of nowhere, we started to encounter all kinds of strange behaviours such as:
- StoreKit2 error (in Xcode)
Received error that does not have a corresponding StoreKit Error: Error Domain=ASDErrorDomain Code=825 "No transactions in response" UserInfo={NSDebugDescription=No transactions in response}
Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=825 "No transactions in response" UserInfo={NSDebugDescription=No transactions in response}
- In some cases the transaction id resulting from the payment was retuned "" or nil, causing our server to raise an exception.
- Newly created sandbox account that was raising an error that says "there is already a subscription made on this apple id".
- Delays in the payment processing
Today, without doing any code changes, we managed to test all the scenarios without encountering any issue.
Due to the oscillating experience we had in the sandbox environment, we are considering postponing the release and maintaining StoreKit 1 for now, but even in this case, the fact that App Store Connect does not offer the possibility of rolling back the Notification Service to v1, causes inconvenience.
Has anyone encountered something similar? Is migrating to v2 a good choice?