Hi, we have PWA for which we´ve built a wrapper using PWA Builder tool and we are experiencing an issue with apple sign in. When we try to redirect the user to "https://appleid.apple.com/auth/authorize?...params...", a bottom sheet login prompt appears and only once the user signs in using the prompt he is then redirected to the url where he needs to sign in again and then we get the callback. We want to get rid of that bottom sheet prompt. The code we´ve tried: ` iosButton.addEventListener('click', function () { window.location.href = "https://appleid.apple.com/auth/authorize?client_id=xxxxx&redirect_uri=xxxxx&response_type=code%20id_token&scope=name%20email&response_mode=form_post"; });` The alternative code we´ve tried for which it seems that nothing happens, we only see the "Started" alert, we´ve confirmed that there is no other error : ` <script src="https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js"></script> <script> (function initAppleSignIn() { try { window.AppleID.auth.init({ clientId: "{{ env('APPLE_WEB_CLIENT_ID') }}", scope: "name email", redirectURI: window.location.origin +"/auth/apple/callback", usePopup: true }); } catch (e) { console.warn('Apple Sign-In init skipped:', e); } })(); function appleButtonClicked() { alert("Started"); try { const res = await window.AppleID.auth.signIn(); } catch (err) { alert("Got error"); } alert("Got here"); } </script>

We have a STEM learning app for kids, and I've been exploring ways to get it listed under the Education Ecosystem Partner (K–12) collection on the App Store. I couldn’t find a clear pathway or guidelines for eligibility. Could you please point me to the relevant documentation or let me know if there's someone I should reach out to for this?

Hello everyone, I hope you are all doing well. I’m opening this discussion because we’ve encountered a repeated Guideline 4.3 rejection for an update, despite having previously addressed the same concern with the App Review team and reaching a resolution. Several weeks ago, we went through a detailed review process regarding Guideline 4.3. We provided full technical explanations, clarified our development structure, redesigned parts of the UI, and made all adjustments requested by the App Review team. That update was ultimately approved, and the app has been live on the App Store since then without any issues. However, our new submission—which includes only a critical bug fix—is now being rejected again for the same 4.3 reason. No changes have been made to the concept, design, or core functionality since the previously approved version. The update is not introducing new features or new UI; it simply resolves a performance bug affecting downloads and uploads, which users are already experiencing in the live version. We operate a single developer account, and our apps are entirely built in-house. Although we use open-source VPN cores (such as Xray-core and Clash), these frameworks are publicly available on GitHub and are commonly used by many developers. Our implementations, configurations, and UI are fully custom and not shared with any other apps. This was already reviewed and confirmed in our previous submission. We have already sent clear and detailed technical explanations through the Resolution Center—similar to what was accepted in our earlier approval—but unfortunately, it hasn’t resolved the issue this time. This situation is becoming difficult for us because: The current live version has a performance bug that users are already affected by. We are in the middle of ongoing campaigns, meaning delays can lead to financial impact. Negative user feedback due to this unresolved bug could permanently damage the app’s reputation. Since this exact concern was previously reviewed, discussed, and resolved with App Review, we are unsure why the same guideline is suddenly being applied to a simple bug-fix update. So I wanted to ask the community: Has anyone faced a similar situation where a previously resolved 4.3 issue resurfaced on later updates? Are there any specific details or approaches that helped clarify the situation for the review team? Is there anything additional we should highlight to prevent misunderstanding on automated or manual review? Any insights or shared experiences from other developers would be extremely valuable. Thank you in advance for your time and support.

Consistent user signals are more important than metadata; they promote favourable reviews, strong retention, and frequent updates to improve ranking. To determine what actually converts on your App Store product page, combine these with A/B testing.

After installing the app from App Store or TestFlight, when the user opens the app and then force-kills it multiple times, the app sometimes gets permanently stuck on a black screen at launch. This issue does NOT happen on Flutter 3.24.5 — works perfectly on all tested iOS devices. The problem started only after migrating to Flutter 3.35.6. This issue happens only in real production installs (App Store / TestFlight). It does not reproduce in Debug mode or through Xcode run / Android Studio run. Expected behavior App should show native splash → render Flutter UI normally. Actual behavior Sometimes after killing the app repeatedly: Native splash shows briefly → then screen turns completely black and stays stuck Steps to Reproduce: Install the app from App Store or TestFlight Launch the app Force-kill the app using app switcher Repeat launch + kill multiple times After 3–7 attempts, app gets stuck on black screen on launch Is this a known issue with the latest Flutter iOS engine? Could this be related to Flutter engine warm-up, pre-warming isolates, or native splash transition? Is there any recommended fix or workaround on iOS side? (e.g., ApplicationDidBecomeActive callbacks, UIWindow setup, GPU thread rendering flush, etc.)

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

Our app (app1) was recently transferred from Team A to Team B. While reviewing the Apple login implementation, we discovered that "Sign in with Apple" had been incorrectly set up to use the Service ID and App ID of another app (app2) — specifically, it was using app2.service as the Service ID and app2 as the App ID. In other words, app1’s users were authenticated through app2’s credentials due to a misconfiguration on our part. Now that app1 has been transferred to Team B, we’re trying to preserve those users. However, app2 is still in Team A, and we cannot maintain Team A anymore — meaning app2 must also be transferred to Team B if we want to retain access to the user data. One idea we considered is submitting app2 for App Review (even though it's non-functional) just to fulfill the transfer requirements, and then transferring it to Team B solely to retain the Apple login setup. Is this approach acceptable? Are there any recommended ways to handle this kind of misconfiguration while preserving existing Sign in with Apple users?

I have an application that I have been attempting to remove from my Apple developer account just to clear it out, unfortunately the latest update was not accepted by apple and was abandoned. I desire to remove the app from my account permanently. I have ensured that all of the requirements at Remove and App have been met, the app was "removed from the app store" more than a year ago. Any advice for actually removing the app would be helpful.

Hi, all. Apparently, it takes around a month and a half after the end of the month for Apple to send the proceeds, but I wish to use third party services which have to be paid at the end of the month. I can sustain the app on my own up to a point, but if so, there's the risk of it dying of success, even though the money is due. Is there a solution to this timing issue? Ideally, I wouldn't want to seek an investment.

Hello, I’m experiencing an issue with App Store search indexing. When searching for “Mergata”, the App Store suggests “Margarita” and shows unrelated results. This creates a lot of friction for users. Has anyone faced a similar issue, and is there a way to request Apple to adjust the search indexing so the app can be found when users type “Mergata”? Any guidance or suggestions would be appreciated.

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I have two questions regarding releasing an app that uses an in-app browser (WKWebView) on the App Store worldwide. Question 1: Encryption usage Our app uses WKWebView and relies on standard encryption. Should this be declared as using encryption during the App Store submission? Question 2: If the answer to Question 1 is YES If it must be declared as using encryption, do we need to prepare and upload additional documentation when submitting the app in France? Also, would this require us to redo the entire build and upload process, even for an app version that has already been uploaded? Goal / request: We want to release an app using WKWebView worldwide, including France. We would like to understand all the necessary steps and requirements for completing the App Store release without unexpected rework. Best regards, P.S.: A similar question was posted a few years ago, but it seems there was no response. https://developer.apple.com/forums/thread/725047 Sadao

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.

Since macOS 15.3.2, we have observed that when another window is moved near the App Store's install button, the button disappears. We have attached a related video in the Feedback submission here https://feedbackassistant.apple.com/feedback/20444423 Our application overlays a transparent, watermark-window on top of the system window, which causes the install button in the App Store to be hidden when a user attempts to install an application.Could you advise on how to avoid this issue?

Hey everyone, I was wondering how it is possible to add screenshots to the app without containing any UI elements, like in the following examples, where the UI is clearly not part of the screenshot: https://apps.apple.com/us/app/komoot-hike-bike-run/id447374873 https://apps.apple.com/us/app/relive-hike-ride-memories/id1201703657 Is the App Review less strict for the first image? Is it somehow connected to the App Preview (but without a video?)? Thanks for the input and help!

Hello, I'm suddenly encountering errors with In-App Purchases (IAP) and my sandbox webhooks, which were working correctly just a few days ago. Specifically: Product Information Error: I'm receiving the following error when trying to fetch product information: { "type": "product_info", "result": "error", "error": "An unknown error occurred" } This API call was functioning normally until today. Sandbox Webhook Failure: I have configured a sandbox webhook, but my server is not receiving any notifications from the App Store. Test API 401: When I attempt to call the test API (https://api.storekit-sandbox.itunes.apple.com/inApps/v1/notifications/test), I consistently receive a 401 (Unauthorized) error. Could you please provide some guidance on how to troubleshoot these issues? Thank you.

Issue: SKOverlay configured with a Custom Product Page identifier opens the default product page instead of the custom one on iOS 26. This works correctly on iOS 18 and earlier. Details: Custom Product Page is published and valid in App Store Connect customProductPageIdentifier is correctly set on SKOverlayAppConfiguration Same code works fine on iOS 18 and lower Code: - (void)presentSKOverlayInWindowScene:(UIWindowScene *)scene { SKOverlayAppConfiguration *config = [[SKOverlayAppConfiguration alloc] initWithAppIdentifier:@"my_app_id" position:SKOverlayPositionBottom]; config.userDismissible = YES; if (@available(iOS 15.0, *)) { [config setCustomProductPageIdentifier:@"my_apps_custom_product_page_id"]; } SKOverlay *overlay = [[SKOverlay alloc] initWithConfiguration:config]; overlay.delegate = self; [overlay presentInScene:scene]; } Are there any known iOS 26 changes affecting Custom Product Pages with SKOverlay, or is additional configuration now required. Thank you

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?