Post

Replies

Boosts

Views

Activity

Unable to sign in to sandbox StoreKit test accounts (iOS)
The error below started today 10/17/2024 (on iOS 18.1 beta 5/6/7 at least) in StoreKit sandbox testing. Outside code/app, I can't even login to the test account in settings->AppStore->Sandbox Account (goes through email/phone confirmation and then silently fails). Tried a different password for a new sandbox test account with no success...Anyone experiencing this? P.S. Status page (https://developer.apple.com/system-status/) shows some related outage from two days ago, but no current problem. Error: Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=530 "(null)" UserInfo={NSUnderlyingError=0x3009ca040 {Error Domain=AMSErrorDomain Code=100 "Authentication Failed The authentication failed." UserInfo={NSMultipleUnderlyingErrorsKey=( "Error Domain=AMSErrorDomain Code=2 "Password reuse not available for account The account state does not support password reuse." UserInfo={NSDebugDescription=Password reuse not available for account The account state does not support password reuse., AMSDescription=Password reuse not available for account, AMSFailureReason=The account state does not support password reuse.}", "Error Domain=AMSErrorDomain Code=306 "Reached max retry count Task reached max retry count (3 / 3);" UserInfo={AMSDescription=Reached max retry count, AMSURL=..., NSDebugDescription=Reached max retry count Task reached max retry count (3 / 3);, AMSFailureReason=Task reached max retry count (3 / 3);, AMSStatusCode=200}" ), AMSDescription=Authentication Failed, NSDebugDescription=Authentication Failed The authentication failed., AMSFailureReason=The authentication failed.}}, storefront-country-code=USA, client-environment-type=Sandbox}
1
0
320
Oct ’24
StoreKit2 currentEntitlements after downgrade followed by upgrade
I'm testing subscription downgrade and upgrade cycles in sandbox, and seeing a behavior I can't explain. Code is generally similar to WWDC sample code for StoreKit2, including listening to incoming transactions. Three entitlement levels, say, Standard, Plus, Pro Corresponding subscription plans all same duration (quarterly) I go through this purchase sequence quickly, Purchase the Pro plan Before the Pro plan expires, purchase the Standard plan Still before the Pro plan expires, purchase the Plus plan Transaction.currentEntitlements after each of the purchases (logged in transaction listener), After step 1: { Pro plan } After Step 2: { (only) Pro plan } After Step 3: { Plus plan , Pro plan } I was expecting to see {Standard, Pro } in entitlements after step 2 (user entitlement calculated from the set is still correct -- Pro). If that's not the case then why after step 3 entitlements includes both Plus and Pro plans?
2
0
178
Oct ’24