Hello, I am really struggling to test my first In-App Purchase for a non-consumable product. I have setup the following: App Store Connect: Paid agreement, Bank account, tax forms and compliance all submitted and active Privacy policy added Pricing and availability - all setup In-App Purchases screen - status is "Ready to Submit" Code refers to the correct BundleID: com.mycompany.product - it is exactly the same in App Store Connect and within my code. XCode: I have setup a StoreKit configuration file and it has correctly sync'd with App Store Connect and pulls through the correct data. The code compiles with no errors or warnings. I trying to initially test in the simulator before I - use a Sandbox account in a spare device. Outcome from all of the above, when I run the app, all I receive is an empty array!! What could I be missing or overlooking? Any help you could offer would be gratefully received. Thanks.

I've followed the setup process to get Apple Hosted Background Assets configured for my project. (https://developer.apple.com/documentation/backgroundassets/downloading-apple-hosted-asset-packs) But when I build and run the app I get the following error... BackgroundAssets/AssetPackManager.swift:174: Fatal error: The process lacks a team ID. I've checked the Signing->Team for both targets and they both have my Team associated. Any help or advice would be appreciated...

We are following up on the previous discussion regarding the 401 Unauthorized response from the production App Store Server API when using sandbox transaction IDs before release. (Reference: https://developer.apple.com/forums/thread/806452) From the Apple staff’s response, we understand that: “Until you have a release in production, access to the production APIs is not allowed. Once you have a release in production this will be unlocked.” We would like to confirm a few technical details related to this point: Q1. Activation timing of production API access At what exact point does access to the production App Store Server API become available? (A) Immediately after App Review approval (status: “Ready for Sale”), but before the app is publicly available on the App Store (B) Only after the app is actually published and visible on the App Store This timing is important for our backend logic that verifies transactions during the review and initial release phases. Q2. Fallback logic between pre-release and post-release Before release, we plan to implement a fallback mechanism that retries sandbox verification when receiving HTTP 401 from the production endpoint. After the app is officially released, we expect that calling the production API with a sandbox transactionId should instead return HTTP 404 Not Found. Is this understanding correct? Should our fallback condition switch from detecting 401 → sandbox (pre-release) to 404 → sandbox (post-release)? Q3. Transition behavior immediately after release When the app transitions from “Ready for Sale” to actually being live on the App Store, is the production API immediately available for real transactions? Or does it take some time (e.g., a few hours) before production access becomes stable? We would appreciate confirmation of: The exact timing when production API access becomes active Whether the 401→404 transition is the expected design behavior Any recommended best practices for handling this transition safely in production systems Thank you for your continued support and clarification.

Hi! We're trying to figure out how to specify a thumbnail image that appears in search results in the new Games app. Currently the thumbnail space just shows the first three preview images from the store page (see the attached file for reference -- our game is Primrows+, at the very top of the screenshot), but other games have a custom-designed image that fills the space and looks nicer, like Welcome to Primrose Lake which you can see at the bottom of the screenshot. I've been searching both the App Store Connect interface and the developer documentation, and I can't find where to set this image or even what this image is called. Here is another screenshot showing the kind of artwork I am trying to create and set in app store connect for our search results: Any help would be appreciated!

What we're trying to implement is not a new subscription promotion It has implemented a function that allows certain members to experience the membership of the application by providing promotional codes. With the offer code provided by Apple, we are currently implemented Log in => Membership provided by the member entering the promotion code => I'm inquiring because I think the next logic will be difficult. There is no way we can identify the member when entering from the app store with Offer code I would like to inquire about developing it so that it does not violate Apple's review regulations as much as possible.

I would like to add adverts into my kids app to make money. Can someone please tell me what ad network they used in their kids app.

In the past Internal builds could not be selected when creating a new version for distribution. The builds appeared in the list but the selection radio buttons used to be disabled. This prevented accidental release of internal versions to the stores I am seeing today that Internal builds can be selected as well. Can we please revert back to the old mechanism

Hello, I’m encountering a confusing issue on macOS related to distributing a notarized app via PKG inside a DMG, built in a Docker environment. Here’s the full workflow: Steps: I build and notarize my macOS app on macOS. I package the app into a PKG and also notarize the PKG. I put the PKG and additional resources into a Docker container. Inside Docker, I download the resources and use genisoimage to create a DMG containing the PKG + resources. I mount the DMG on macOS, then double-click the PKG inside the DMG to install the app. After installation, when I try to open the app, macOS reports: “App is damaged and can’t be opened. You should move it to the Trash.” However, if I first copy the PKG from the DMG to /tmp via a script, then run the installation, the app opens and runs correctly. Observations: Both the app and PKG are properly notarized. This only happens when installing directly from the DMG built via Docker + genisoimage. Copying to a temporary location seems to bypass the issue. Using hdiutil to create the DMG may mitigate the issue, but I need to reproduce this in a Docker-based CI/CD workflow. Questions: Why does installing a notarized PKG directly from a DMG generated in Docker via genisoimage sometimes cause macOS to report the app as damaged? Could this be related to quarantine/xattr, permissions, or some subtle notarization issue when creating DMGs in Docker? What is the recommended way to structure DMG + PKG in an automated environment to ensure Gatekeeper and notarization work correctly? Thanks in advance for any insights or guidance!

I attempted to create an ad campaign for an app in the MacOS App Store, but the Apple ads website does not seem to allow this. The Apple ads website seems to assume that my app is in the iOS App Store. Clearly the MacOS App Store is not a priority, but this has been unreasonably difficult and confusing. Can someone please tell me if Search ads in the MacOS App Store are supported, and if so, how can I access this support?

Hello everyone, I’m currently experiencing an issue where no subscriptions appear in my app when fetching products from StoreKit via react-native-iap. I would like to confirm whether this is related to my App Store Connect setup or a possible StoreKit limitation. Context My app uses react-native-iap and successfully initializes the StoreKit connection with: await RNIap.initConnection(); const items = await RNIap.fetchProducts({ skus: productIds, type: 'subs', }); productIds contains valid identifiers matching those configured in App Store Connect. The API /plan dynamically returns the correct product IDs. The fetch call completes successfully, but returns an empty array ([]). What I have already done Confirmed all subscription products exist and are correctly linked to the same app bundle ID. All subscriptions are currently in “Waiting for Review” status in App Store Connect. Verified that StoreKit connection is initialized correctly (RNIap.initConnection() returns successfully). Tested on a real device (iPhone 14, iOS 18). Contacted App Review by phone — they confirmed my implementation was correct and told me that pending subscriptions should still appear for review. Followed Apple’s official guides: TN3186: Troubleshooting in-app purchase availability in the sandbox TN3188: Troubleshooting in-app purchase availability in the App Store Unfortunately, neither solved the issue. Code excerpt Here’s the relevant portion of my React Native code: await RNIap.initConnection(); let items = await RNIap.fetchProducts({ skus: productIds, type: 'subs', }); setProducts(items); console.log('🛍️ Products from Store:', items); Everything runs fine, no errors — but items is always empty. Question Could this be due to the fact that my subscriptions are still Waiting for Review (not yet “Ready for Sale”)? If yes, is there any way for the App Review or developer testing environment to see them before they are approved? Or could I be missing a configuration step (for example, enabling the App-Specific Shared Secret or App Store server notifications)? Any advice from someone who has faced this issue or from Apple staff would be greatly appreciated 🙏 Environment React Native 0.76 react-native-iap 13.7.0 iOS 18.1 (real device) Xcode 16 Products: Auto-renewable subscriptions Status: “Waiting for Review” App currently in App Review Thank you, Sébastien

Hi Everybody! I would like to develop an iOS app with MDM features and distribute it on App Store. The problem I got stuck with is how to QA-test the MDM features of such an app. The app is not yet on App Store, it's under development. I can upload builds to App Store Connect, invite testers, they can test the app using TestFlight, all fine. But features that require an MDM configuration don't work since the app is not deployed via an MDM solution. It cannot be deployed via MDM since it's not an enterprise app and it's not on App Store yet. There are ways to work around this only for dev-testing (like a hardcoded configuration) but I need to give this to QA engineers. AI answers suggest that Custom Apps in ASM/ABM might be the way out of this. Apple docs say I need to have the app reviewed by Apple first, only then can I assign it to organizations. But again, I need this for internal testing the app before releasing it. And before having to submit the build to Apple for approval. I am quite sure it's possible to do this, there are apps on App Store with such features (Jamf Self Service), and other platforms provide a way (private store on Android) for internal testing, but I haven't been able to find the Apple solution yet. Any help would be appreciated. Best regards, Balazs

We’re preparing our 2026 iOS development roadmap and need clarification on upcoming App Store submission requirements related to Xcode versions. Our team plans to migrate our apps to Xcode 26 by December 2025, and we’ve seen references indicating that Xcode 26 or later may become mandatory for App Store submissions starting April 2026. Could Apple please confirm: 1. Whether April 2026 is the official enforcement date after which builds created with earlier versions of Xcode (e.g., Xcode 16.x) will no longer be accepted for App Store submission. 2. Whether there will be any grace period or continued acceptance for builds created with older versions of Xcode beyond that date. We want to ensure our upgrade plans and release timelines are aligned with Apple’s official submission policies to prevent any disruption to our delivery schedules. Thank you for your guidance.

We’ve recently changed the name of our published app from “Gourmet Society Lloyds” to “Gourmet Society”. The current App Store link is: https://apps.apple.com/gb/app/gourmet-society-lloyds/id6447692472 After the name change, we expect the URL to look like this: https://apps.apple.com/gb/app/gourmet-society/id6447692472 However, we’re not sure whether Apple automatically updates the App Store URL (the text part before the ID) when the app name changes, and whether the old URL will continue to redirect to the new one. I couldn’t find any official Apple documentation confirming this behavior. Could someone from Apple clarify how App Store URLs are handled in such cases? Thanks in advance! Zoltan

Love the new web-based App Store that launched today! I’m really hoping Apple will eventually provide a JSON/REST API for search results. Google doesn’t officially offer one either, but because of how the Play Store works for Chrome and Android, developers can use a third-party library like google-play-scraper. For small independent developers like myself, it’s a bit of a disadvantage being priced out of expensive data brokers such as Sensor Tower, who are obviously scraping the App Store anyway. It’s also uncomfortable knowing those companies harvest data from App Store Connect while charging us to access analytics based on our own apps. Would it be too much to ask for an official—or even semi-official—way to retrieve country-specific keyword rankings for apps?

Xcode SPM (Swift Package Manager) Error I added the "Apple App Store Server Swift Library" library to Xcode using Swift Package Manager. Both the project and target are set to iOS 14 or higher. However, when I build after adding the library, an error occurs with the library. A message appears stating that the target is set to iOS 12. I'm using Xcode 26.0.1. Even after adding it to all my projects, the build continues with the same error. I've tried building the library from version 1.0.0 to the latest version, but the same error persists. Even after completely cleaning the project and running it, the same error persists. Does anyone know how to fix this?

Hi, I have an application published in the Marketplace. I made certain updates to the app. I did my tests.No problem. I did my tests via Testflight. There is no problem I encountered. But my app update request was returned by app review. The answer i got from them ;  "Specifically, our login attempt displayed loading indefinitely; we were unable to access the app features and functionality." Here are the ways that I tried and the app worked successfully. Connect from America using VPN.No problem, it works. I connected from using IPV6.No problem, it works. I tried with simulator.No problem, it works. I tried real device.No problem , it works. I tried testflight.No problem, it works. I tired version 15.2 and earlier.No problem , it works. I have no idea why apple staff are getting this error. Has anyone encountered such a problem before? What solutions would you suggest? I'm waiting for your help.

Dear Experts, If a user with an older device tries to download an app, and the current version of the app requires an iOS version which their device does not support, the App Store will offer them an older most-recent-compatible version instead. I've just had an enquiry from a user of my app for whom this has not worked. Specifically he has an iPad 2. He foolishly deleted my app from the device, and now the App Store will not let him re-install it. Does anyone know why this may be? Is it simply that this App Store feature does not work for devices as old as the iPad 2? Thanks.

When I try to submit a new app version, I get this message: "The Apple Developer Program License Agreement has been updated and needs to be reviewed. In order to update your existing apps and submit new apps, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website." But I have signed the latest agreement and cannot find anything else to sign. On the main page (https://developer.apple.com/account) there is no longer a notification about an agreement to sign.

When I try to distrubte app by xcode I am getting error from below. I've already checked all my agreements in App Connect, and my Apple ID is an admin, but I still get this error and cannot distribute my new app version. AppsService: ResponseErrors (1): Error status: 403, code: FORBIDDEN_ERROR, title: 'This request is forbidden for security reasons', detail: 'The API key in use does not allow this request', id: 02b244d3-7a49-4e66-8591-ab399a7cdb33

Hi, I recently make an app for my podcast, news, and music without copyright and you not accept why you say Rechazado 1.5.0 Safety: Developer Information 5.2.3 Legal: Intellectual Property - Audio/Video Downloading I dont make app for download, only stream my podcast live, news information and music without copyright. Now I like to make radio podcast, interviews, etc What I need for you accept? Thanks