Search results for

“sandbox”

10,542 results found

Post

Replies

Boosts

Views

Activity

App storefront fetching US even though devices of testers are from India
Does TestFlight's sandbox resolves storefront differently from production — because if it does, my production launch will be unaffected and this is a testing artefact. Right now, the storefront always resolves as US and fetches USD pricing, even though in my AppStoreConnect, availability and pricing country is restricted to India alone, and ideally the fetch to my subscription page shoul dbe in Indian Rupee. Any observations, any one please?
0
0
189
Jul ’26
AppTransaction.shared fails with SKServerErrorDomain Code=-1 across all install methods (sandbox) — stumped after ruling out everything checkable
Hi all, I've been debugging a persistent sandbox StoreKit issue for a while now and have ruled out everything I can check from my end. Posting the full picture here in case anyone recognizes this pattern or has advice — genuinely stuck. The core problem AppTransaction.shared (StoreKit 2) consistently fails with: Error Domain=SKServerErrorDomain Code=-1 (null) UserInfo={storefront-country-code=AUS, client-environment-type=Sandbox} A real purchase attempt separately fails with: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={storefront-country-code=AUS, AMSServerErrorCode=3504, client-environment-type=Sandbox} What's confirmed working (so I can rule these out as the cause) Product catalog/pricing fetch — real price, title, currency load correctly every time canMakePayments → true getStorefront → AUS, correctly App Store Connect account: Paid Apps Agreement Active, Free Apps Agreement Active, bank account Active, all 3 tax forms Active (ABN/GST, Certifi
1
0
419
Jul ’26
Storekit Returns 0 product identifier in product Array.
Am same facing Storekit issue 0 product returns in Product identifier Array. Even i test on device it returns invalid product identifier due to 0 product array. Issue Description Step 1 Create a new Auto-Renewable Subscription from the App Information page in App Store Connect. Step 2 Complete all the required fields for the Auto-Renewable Subscription and click the Save button. Expected Result After saving, the subscription status should change from Prepare for Submission to Ready to Submit. Actual Result The subscription status remains Prepare for Submission and does not change to Ready to Submit, even though all required information has been completed and the subscription has been saved. I am currently facing a critical issue while creating an Auto-Renewable Subscription in App Store Connect. I have already completed all the required subscription details. However, whenever I click the Save button, the subscription status does not change from Prepare for Submission to Ready to Submit, as expected. Because t
1
0
1k
Jul ’26
StoreKit 2: products load with correct prices but purchase fails immediately with "Item Unavailable" (app not yet approved)
Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with Item Unavailable. No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with Item Unavailable for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products do not need prior approval to function in review, but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:
2
0
1.2k
Jul ’26
Reply to Accessing preferences in another app's sandbox - operation denied and NSAppDataUsageDescription never shows
I like your suggestion, but I just tried it and it seems that ~/Library/Application Support/ is re-routed inside the container, e.g. let rawPath = ~/Application Support/com.example/(self.bundleID).plist let path = (rawPath as NSString).expandingTildeInPath let url = URL(fileURLWithPath: path) guard let dict = NSDictionary(contentsOf: url) as? [String: Any] else { print(Error: Failed to read or parse plist at: (path)) When run in context of a .saver running inside LegacyScreenSaver, this happens: Failed to read or parse plist at: /Users/username/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver.x86-64/Data/Application Support/com.example/com.example.foobar.plist I did another test where, instead of using ~/Library/Application Support/ I used /Users/Shared/com.example and that one seemed to work. Using /Users/Shared/ is not very elegant, but seems to be a location of last resort that some other apps use in some cases. Am I missing something? Is there a way from inside a sandbox, to get
Topic: Privacy & Security SubTopic: General Tags:
Jul ’26
ASDServerErrorDomain Code 3504 when purchasing non-consumable IAP
I am experiencing an issue with a non-consumable in-app purchase in my iOS app. The product loads correctly from the App Store and is displayed in the app, but when attempting to complete the purchase, StoreKit returns the following error: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={ NSLocalizedFailureReason=This item cannot be found., AMSServerErrorCode=3504, client-environment-type=Sandbox, storefront-country-code=USA } The same issue was also encountered by the App Review tester when they attempted to purchase the non-consumable product during review. The product: Is correctly configured in App Store Connect Has active pricing Is available in the United States Was included in the app submission Loads successfully and displays the correct price Fails only when the purchase is initiated Since the product metadata can be retrieved successfully, but the transaction fails with “This item cannot be found,” this appears to be a possible i
3
0
1.1k
Jul ’26
Sandbox Apple Account sign-in asks for phone verification, then fails with “Could not connect to iCloud”
Hi, I created a Sandbox Apple Account in App Store Connect for testing StoreKit / Age Assurance sandbox scenarios. When I try to sign in on an iPhone through: Settings -> Developer -> Sandbox Apple Account I can enter the sandbox account email/password and I successfully receive the email verification code. After entering the email verification code, iOS asks me to add/verify a phone number. When I enter the phone number, I get this error: “Could not connect to iCloud. Verification codes cannot be sent to this phone number at this time. Please try again later.” I did not set any phone number when creating the sandbox tester in App Store Connect. The sandbox tester was created with only name, email, password, and country/region. Context: iPhone has Developer Mode enabled I am signing in via Settings -> Developer -> Sandbox Apple Account I am not trying to sign in through normal iCloud / Apple Account settings The sandbox accoun
0
0
443
Jul ’26
Reply to StoreKit returns no in-app subscriptions on TestFlight despite correct App Store Connect configuration
I am also having the same problem. Subscriptions products are not arriving. Non-consumable in-app purchases arriving only when they are Ready for Review state but i am not able to complete a purchase, and when i try to complete a purchase i get; Payment completed with error: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={NSLocalizedFailureReason=This item cannot be found., AMSServerErrorCode=3504, client-environment-type=Sandbox, storefront-country-code=USA}
Topic: App & System Services SubTopic: StoreKit Tags:
Jul ’26
Reply to Accessing preferences in another app's sandbox - operation denied and NSAppDataUsageDescription never shows
[quote='898974022, XMI, /thread/839190?answerId=898974022#898974022, /profile/XMI'] I agree that using Appex format would be ideal. I submitted FB24013514 [/quote] Thank you. [quote='898974022, XMI, /thread/839190?answerId=898974022#898974022, /profile/XMI'] As for workarounds using legacyScreenSaver [/quote] Yeah, that’s basically the direction I was gonna send you. It works because the process that loads and runs your screen saver isn’t tightly sandboxed [1]. The only question is whether it’s better to continue using the preferences subsystem or whether you can store this state in a file that’s entirely under your control (so a property list in ~/Library/Application Support/YOUR_PRODUCT_NAME). Honestly, I’d lean towards the latter. It has various benefits: It’s in the user’s home directory, so each user gets their own preferences. And you don’t need privilege escalation to write it. And while I can’t predict the future with 100% fidelity, my experience is that completely custom stuff is less likely
Topic: Privacy & Security SubTopic: General Tags:
Jul ’26
Advanced Commerce REACTIVATE_SUBSCRIPTION intermittently fails with StoreKit.InvalidRequestError code 1
Hello, We are using Apple’s Advanced Commerce API and are seeing intermittent failures when reactivating a subscription from the app using REACTIVATE_SUBSCRIPTION. Reproduction flow: Purchase a regular StoreKit auto-renewable subscription. Migrate the subscription to Advanced Commerce. Disable auto-renewal from Apple’s native subscription settings. Return to the app and try to reactivate the subscription from our subscription settings page. This exact flow was working successfully few days ago. The payload structure has not changed, but the same flow now sometimes works and sometimes fails with: Error Domain=StoreKit.InvalidRequestError Code=1 The operation couldn’t be completed. (StoreKit.InvalidRequestError error 1.) userInfo=[:] We reproduced this with a newly created Sandbox Apple Account and a newly purchased/migrated subscription. Questions: Is there a known issue with Advanced Commerce reactivation? What does StoreKit.InvalidRequestError code 1 mean in this context? Is there a way to get the u
0
0
482
Jul ’26
Sandbox: valid IAP product identifier returns invalid product or bundle identifier
Hello, My TestFlight app cannot load any in-app purchase products in Sandbox. App: AI Photo Toolkit Pro Bundle ID: com.mengjuanhuang.aiphototoolkit TestFlight build: 1.1 (5) Product IDs: com.mengjuanhuang.aiphototoolkit.pro.lifetime com.mengjuanhuang.aiphototoolkit.pro.monthly com.mengjuanhuang.aiphototoolkit.pro.yearly The products are configured in App Store Connect with localization, pricing, US availability, screenshots, review notes, and an active Paid Applications Agreement. The IAPs and subscription group were submitted with the app version. A US Sandbox Apple Account is signed in on a real device. Using Settings > Developer > Sandbox Apple Account > Initiate Transaction with: Product ID: com.mengjuanhuang.aiphototoolkit.pro.lifetime Bundle ID: com.mengjuanhuang.aiphototoolkit returns: “The provided product identifier or bundle identifier is invalid.” [Environment: Sandbox] The TestFlight paywall also receives an empty product list. The bundle ID and product
0
0
191
Jul ’26
App Store Server Notifications still use old callback URL after successful update
Hello, I’m experiencing an issue with App Store Server Notifications Version 2 in the sandbox environment. Initially, an old sandbox callback URL was configured. I then replaced it with a new callback URL in App Store Connect. The new URL was saved successfully, but newly created sandbox TEST notifications continued to be sent to the old URL. To investigate further, I removed both the production and sandbox callback URLs completely. App Store Connect showed both fields as empty, and the App Store Connect API returned null for the corresponding URL attributes. However, newly created sandbox TEST notifications were still sent to the same old URL. I later used the “Modify an App” API to configure the new production and sandbox callback URLs. The PATCH request returned HTTP 200, and a subsequent GET request confirmed the new URLs and Version 2 settings. Despite this, new sandbox TEST notifications continued to use the old hostname in the HTTP Host hea
0
0
350
Jul ’26
Help: Invalid In-App Purchase Products
I have verified that the Paid Apps Agreement, bank account details, tax forms, compliance and other related information are all valid. I created two IAP products using identical configurations. One can be purchased normally, while the other returns an invalid product error. Moreover, any newly created products still trigger the same invalid product error. I have attempted multiple troubleshooting steps: clearing purchase records for sandbox testers, creating new sandbox accounts, uninstalling the app, and restarting devices. Unfortunately, I have still not identified the root cause. I hope to receive additional troubleshooting guidance.
1
0
234
Jul ’26
Sandbox can purchase auto-renewable subscriptions but non-consumable IAP is always invalid
I’m testing In-App Purchases in the sandbox on a real iPhone. Auto-renewable subscriptions work correctly with the same app build, bundle ID, and sandbox tester account: com.aifalling.sides.vip.monthly com.aifalling.sides.vip.yearly However, a non-consumable product can’t be purchased: Product ID: com.aifalling.sides.vip.onetime App Store Connect IAP Apple ID: 6794812888 Type: Non-Consumable Status: Ready to Submit Bundle ID: com.aifalling.sides The native StoreKit payment request fails immediately with: The purchase identifier was invalid. The wrapper reports error code 700605. I verified the non-consumable product through the App Store Connect API: Product ID exists and is returned by the API One localization exists: zh-Hans A price schedule is configured, including a base territory and prices Availability includes China (CHN) and many other territories availableInNewTerritories is true I waited more than one hour after the latest metadata changes I completely removed the app, rebuilt/rein
1
0
768
Jul ’26
APNs device token never delivered — didRegisterForRemoteNotifications never fires (works fine for other apps on same device)
Summary On a physical iPhone, the app never receives an APNs device token (application:didRegisterForRemoteNotificationsWithDeviceToken: never fires, even after waiting 60 seconds after login and calling registerForRemoteNotifications). The symptom reproduces identically in two different apps (different bundle IDs, same Team), over both WiFi and cellular data, even after a full device restart. Other apps on the same device (WhatsApp, Gmail, etc.) receive push notifications normally. Account details Team ID: 6NJN39FM4A Program: Apple Developer Program (Individual), active through June 26, 2027, no pending payments or agreements Signing Apple ID: my developer Apple ID (account in good standing) Affected apps (same issue in both) com.movicolombia.driver com.movicolombia.passenger For both App IDs, in Certificates, Identifiers & Profiles, the Push Notifications capability is checked/enabled (Environment: Sandbox & Production, Key Restriction: Team Scoped). Test device Physical iPhone, iOS 26.5.2,
1
0
482
Jul ’26
App storefront fetching US even though devices of testers are from India
Does TestFlight's sandbox resolves storefront differently from production — because if it does, my production launch will be unaffected and this is a testing artefact. Right now, the storefront always resolves as US and fetches USD pricing, even though in my AppStoreConnect, availability and pricing country is restricted to India alone, and ideally the fetch to my subscription page shoul dbe in Indian Rupee. Any observations, any one please?
Replies
0
Boosts
0
Views
189
Activity
Jul ’26
AppTransaction.shared fails with SKServerErrorDomain Code=-1 across all install methods (sandbox) — stumped after ruling out everything checkable
Hi all, I've been debugging a persistent sandbox StoreKit issue for a while now and have ruled out everything I can check from my end. Posting the full picture here in case anyone recognizes this pattern or has advice — genuinely stuck. The core problem AppTransaction.shared (StoreKit 2) consistently fails with: Error Domain=SKServerErrorDomain Code=-1 (null) UserInfo={storefront-country-code=AUS, client-environment-type=Sandbox} A real purchase attempt separately fails with: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={storefront-country-code=AUS, AMSServerErrorCode=3504, client-environment-type=Sandbox} What's confirmed working (so I can rule these out as the cause) Product catalog/pricing fetch — real price, title, currency load correctly every time canMakePayments → true getStorefront → AUS, correctly App Store Connect account: Paid Apps Agreement Active, Free Apps Agreement Active, bank account Active, all 3 tax forms Active (ABN/GST, Certifi
Replies
1
Boosts
0
Views
419
Activity
Jul ’26
Storekit Returns 0 product identifier in product Array.
Am same facing Storekit issue 0 product returns in Product identifier Array. Even i test on device it returns invalid product identifier due to 0 product array. Issue Description Step 1 Create a new Auto-Renewable Subscription from the App Information page in App Store Connect. Step 2 Complete all the required fields for the Auto-Renewable Subscription and click the Save button. Expected Result After saving, the subscription status should change from Prepare for Submission to Ready to Submit. Actual Result The subscription status remains Prepare for Submission and does not change to Ready to Submit, even though all required information has been completed and the subscription has been saved. I am currently facing a critical issue while creating an Auto-Renewable Subscription in App Store Connect. I have already completed all the required subscription details. However, whenever I click the Save button, the subscription status does not change from Prepare for Submission to Ready to Submit, as expected. Because t
Replies
1
Boosts
0
Views
1k
Activity
Jul ’26
StoreKit 2: products load with correct prices but purchase fails immediately with "Item Unavailable" (app not yet approved)
Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with Item Unavailable. No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with Item Unavailable for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products do not need prior approval to function in review, but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:
Replies
2
Boosts
0
Views
1.2k
Activity
Jul ’26
Reply to Accessing preferences in another app's sandbox - operation denied and NSAppDataUsageDescription never shows
I like your suggestion, but I just tried it and it seems that ~/Library/Application Support/ is re-routed inside the container, e.g. let rawPath = ~/Application Support/com.example/(self.bundleID).plist let path = (rawPath as NSString).expandingTildeInPath let url = URL(fileURLWithPath: path) guard let dict = NSDictionary(contentsOf: url) as? [String: Any] else { print(Error: Failed to read or parse plist at: (path)) When run in context of a .saver running inside LegacyScreenSaver, this happens: Failed to read or parse plist at: /Users/username/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver.x86-64/Data/Application Support/com.example/com.example.foobar.plist I did another test where, instead of using ~/Library/Application Support/ I used /Users/Shared/com.example and that one seemed to work. Using /Users/Shared/ is not very elegant, but seems to be a location of last resort that some other apps use in some cases. Am I missing something? Is there a way from inside a sandbox, to get
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’26
ASDServerErrorDomain Code 3504 when purchasing non-consumable IAP
I am experiencing an issue with a non-consumable in-app purchase in my iOS app. The product loads correctly from the App Store and is displayed in the app, but when attempting to complete the purchase, StoreKit returns the following error: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={ NSLocalizedFailureReason=This item cannot be found., AMSServerErrorCode=3504, client-environment-type=Sandbox, storefront-country-code=USA } The same issue was also encountered by the App Review tester when they attempted to purchase the non-consumable product during review. The product: Is correctly configured in App Store Connect Has active pricing Is available in the United States Was included in the app submission Loads successfully and displays the correct price Fails only when the purchase is initiated Since the product metadata can be retrieved successfully, but the transaction fails with “This item cannot be found,” this appears to be a possible i
Replies
3
Boosts
0
Views
1.1k
Activity
Jul ’26
Sandbox Apple Account sign-in asks for phone verification, then fails with “Could not connect to iCloud”
Hi, I created a Sandbox Apple Account in App Store Connect for testing StoreKit / Age Assurance sandbox scenarios. When I try to sign in on an iPhone through: Settings -> Developer -> Sandbox Apple Account I can enter the sandbox account email/password and I successfully receive the email verification code. After entering the email verification code, iOS asks me to add/verify a phone number. When I enter the phone number, I get this error: “Could not connect to iCloud. Verification codes cannot be sent to this phone number at this time. Please try again later.” I did not set any phone number when creating the sandbox tester in App Store Connect. The sandbox tester was created with only name, email, password, and country/region. Context: iPhone has Developer Mode enabled I am signing in via Settings -> Developer -> Sandbox Apple Account I am not trying to sign in through normal iCloud / Apple Account settings The sandbox accoun
Replies
0
Boosts
0
Views
443
Activity
Jul ’26
Reply to StoreKit returns no in-app subscriptions on TestFlight despite correct App Store Connect configuration
I am also having the same problem. Subscriptions products are not arriving. Non-consumable in-app purchases arriving only when they are Ready for Review state but i am not able to complete a purchase, and when i try to complete a purchase i get; Payment completed with error: Error Domain=ASDServerErrorDomain Code=3504 This item cannot be found. UserInfo={NSLocalizedFailureReason=This item cannot be found., AMSServerErrorCode=3504, client-environment-type=Sandbox, storefront-country-code=USA}
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
Jul ’26
Reply to Accessing preferences in another app's sandbox - operation denied and NSAppDataUsageDescription never shows
[quote='898974022, XMI, /thread/839190?answerId=898974022#898974022, /profile/XMI'] I agree that using Appex format would be ideal. I submitted FB24013514 [/quote] Thank you. [quote='898974022, XMI, /thread/839190?answerId=898974022#898974022, /profile/XMI'] As for workarounds using legacyScreenSaver [/quote] Yeah, that’s basically the direction I was gonna send you. It works because the process that loads and runs your screen saver isn’t tightly sandboxed [1]. The only question is whether it’s better to continue using the preferences subsystem or whether you can store this state in a file that’s entirely under your control (so a property list in ~/Library/Application Support/YOUR_PRODUCT_NAME). Honestly, I’d lean towards the latter. It has various benefits: It’s in the user’s home directory, so each user gets their own preferences. And you don’t need privilege escalation to write it. And while I can’t predict the future with 100% fidelity, my experience is that completely custom stuff is less likely
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’26
Advanced Commerce REACTIVATE_SUBSCRIPTION intermittently fails with StoreKit.InvalidRequestError code 1
Hello, We are using Apple’s Advanced Commerce API and are seeing intermittent failures when reactivating a subscription from the app using REACTIVATE_SUBSCRIPTION. Reproduction flow: Purchase a regular StoreKit auto-renewable subscription. Migrate the subscription to Advanced Commerce. Disable auto-renewal from Apple’s native subscription settings. Return to the app and try to reactivate the subscription from our subscription settings page. This exact flow was working successfully few days ago. The payload structure has not changed, but the same flow now sometimes works and sometimes fails with: Error Domain=StoreKit.InvalidRequestError Code=1 The operation couldn’t be completed. (StoreKit.InvalidRequestError error 1.) userInfo=[:] We reproduced this with a newly created Sandbox Apple Account and a newly purchased/migrated subscription. Questions: Is there a known issue with Advanced Commerce reactivation? What does StoreKit.InvalidRequestError code 1 mean in this context? Is there a way to get the u
Replies
0
Boosts
0
Views
482
Activity
Jul ’26
Sandbox: valid IAP product identifier returns invalid product or bundle identifier
Hello, My TestFlight app cannot load any in-app purchase products in Sandbox. App: AI Photo Toolkit Pro Bundle ID: com.mengjuanhuang.aiphototoolkit TestFlight build: 1.1 (5) Product IDs: com.mengjuanhuang.aiphototoolkit.pro.lifetime com.mengjuanhuang.aiphototoolkit.pro.monthly com.mengjuanhuang.aiphototoolkit.pro.yearly The products are configured in App Store Connect with localization, pricing, US availability, screenshots, review notes, and an active Paid Applications Agreement. The IAPs and subscription group were submitted with the app version. A US Sandbox Apple Account is signed in on a real device. Using Settings > Developer > Sandbox Apple Account > Initiate Transaction with: Product ID: com.mengjuanhuang.aiphototoolkit.pro.lifetime Bundle ID: com.mengjuanhuang.aiphototoolkit returns: “The provided product identifier or bundle identifier is invalid.” [Environment: Sandbox] The TestFlight paywall also receives an empty product list. The bundle ID and product
Replies
0
Boosts
0
Views
191
Activity
Jul ’26
App Store Server Notifications still use old callback URL after successful update
Hello, I’m experiencing an issue with App Store Server Notifications Version 2 in the sandbox environment. Initially, an old sandbox callback URL was configured. I then replaced it with a new callback URL in App Store Connect. The new URL was saved successfully, but newly created sandbox TEST notifications continued to be sent to the old URL. To investigate further, I removed both the production and sandbox callback URLs completely. App Store Connect showed both fields as empty, and the App Store Connect API returned null for the corresponding URL attributes. However, newly created sandbox TEST notifications were still sent to the same old URL. I later used the “Modify an App” API to configure the new production and sandbox callback URLs. The PATCH request returned HTTP 200, and a subsequent GET request confirmed the new URLs and Version 2 settings. Despite this, new sandbox TEST notifications continued to use the old hostname in the HTTP Host hea
Replies
0
Boosts
0
Views
350
Activity
Jul ’26
Help: Invalid In-App Purchase Products
I have verified that the Paid Apps Agreement, bank account details, tax forms, compliance and other related information are all valid. I created two IAP products using identical configurations. One can be purchased normally, while the other returns an invalid product error. Moreover, any newly created products still trigger the same invalid product error. I have attempted multiple troubleshooting steps: clearing purchase records for sandbox testers, creating new sandbox accounts, uninstalling the app, and restarting devices. Unfortunately, I have still not identified the root cause. I hope to receive additional troubleshooting guidance.
Replies
1
Boosts
0
Views
234
Activity
Jul ’26
Sandbox can purchase auto-renewable subscriptions but non-consumable IAP is always invalid
I’m testing In-App Purchases in the sandbox on a real iPhone. Auto-renewable subscriptions work correctly with the same app build, bundle ID, and sandbox tester account: com.aifalling.sides.vip.monthly com.aifalling.sides.vip.yearly However, a non-consumable product can’t be purchased: Product ID: com.aifalling.sides.vip.onetime App Store Connect IAP Apple ID: 6794812888 Type: Non-Consumable Status: Ready to Submit Bundle ID: com.aifalling.sides The native StoreKit payment request fails immediately with: The purchase identifier was invalid. The wrapper reports error code 700605. I verified the non-consumable product through the App Store Connect API: Product ID exists and is returned by the API One localization exists: zh-Hans A price schedule is configured, including a base territory and prices Availability includes China (CHN) and many other territories availableInNewTerritories is true I waited more than one hour after the latest metadata changes I completely removed the app, rebuilt/rein
Replies
1
Boosts
0
Views
768
Activity
Jul ’26
APNs device token never delivered — didRegisterForRemoteNotifications never fires (works fine for other apps on same device)
Summary On a physical iPhone, the app never receives an APNs device token (application:didRegisterForRemoteNotificationsWithDeviceToken: never fires, even after waiting 60 seconds after login and calling registerForRemoteNotifications). The symptom reproduces identically in two different apps (different bundle IDs, same Team), over both WiFi and cellular data, even after a full device restart. Other apps on the same device (WhatsApp, Gmail, etc.) receive push notifications normally. Account details Team ID: 6NJN39FM4A Program: Apple Developer Program (Individual), active through June 26, 2027, no pending payments or agreements Signing Apple ID: my developer Apple ID (account in good standing) Affected apps (same issue in both) com.movicolombia.driver com.movicolombia.passenger For both App IDs, in Certificates, Identifiers & Profiles, the Push Notifications capability is checked/enabled (Environment: Sandbox & Production, Key Restriction: Team Scoped). Test device Physical iPhone, iOS 26.5.2,
Replies
1
Boosts
0
Views
482
Activity
Jul ’26