Requesting you all any recommendations for iOS ASO tools covering keyword research, metadata optimisation, competitor tracking, and A/B testing.

Can't Edit Age Ratings in App Information Section of App Store Connect for released App Versions. I only have option to View. I think some of the Age Rating questions are still unanswered but when I view them, I can't Edit them. Non-released apps of mine in App Store Connect allow me to edit answers to the Age Ratings questions but I can only View Age Rating questions for released apps. Do I have to create a new version/build and submit to App Store Connect to be able to Edit the Age Questions?

Hi everyone, my name is Donovan, I am sharing here the official response I received from Apple following my appeal with App Review Board (image attached). For context, I am an independent developer and a student, working alone. This application was originally created as a student project, with a very simple goal: to improve my skills in mobile application development and to understand the entire creation cycle, from the initial idea to a genuinely usable application. What was meant to be an exercise gradually became a real product. Over time, many people tested the project, used it, provided positive feedback, and encouraged me to take it all the way. That is why I decided to continue it, structure it properly, and finalize it with the level of seriousness expected from a public-facing application. Today, the application is a dating and social connection app, entirely free, with no blocking paid features, funded only by light and optional advertising. It follows the rules, works correctly, and offers features that Apple itself acknowledged as useful and informative. And yet, after review, the message is clear: it is not the quality that is being questioned, but the category. Because it is a dating app, a category considered saturated, two years of independent, self-funded work, carried out seriously and in compliance with the rules, can simply be dismissed. What is being judged here is not the work itself. It is the right to enter. The “unique and very high-quality experience” being required appears to be a threshold reserved for those who are already established, visible, or funded. For a serious student project carried by a single developer, the door remains closed, cleanly, politely, definitively. For those who still wish to see what the application looks like, I have attached a few images illustrating the interface and the main features. Unfortunately, this will likely be the only way to discover it on iOS. Under these conditions, the conclusion is pragmatic. Rather than continuing to defend the very existence of an honest and free project, it becomes more coherent to invest my energy where it is genuinely accepted. On its side, Android validated the project without difficulty. It still allows an independent developer to propose an idea, let it evolve, and bring it to completion without requiring prior success just to earn the right to try. It is therefore very likely that these two years of development will never make it to the App Store. Not out of frustration. Out of clarity. I am publishing this message not to provoke, but to inform other independent developers: Apple is a remarkable platform, provided you are already established on it. And this is a reality worth knowing before turning a student project into a life project. Screenshots:

I’m testing auto-renewable subscription purchases in the sandbox environment. When I buy a subscription package using a sandbox test user, I don’t receive any App Store Server Notifications from the sandbox. However, when I use the “Request Test Notification” option in App Store Connect, the notification is received successfully. My sandbox server notification URL is configured correctly and publicly accessible. I also call finishTransaction() after purchase, and the receipt is verified successfully with the sandbox verification endpoint. To further debug, I used the getNotificationHistory API to fetch notifications for yesterday and today (Nov 3–4, 2025). Apple’s API response does not include any notifications or transaction IDs for my today’s purchases (Nov 4, 2025) — even though I can confirm from logs that those transactions were completed and verified successfully. It looks like sandbox purchase notifications are not being sent or logged, even though test notifications work fine. Could someone from Apple please confirm if there’s currently an issue with sandbox server notifications for auto-renewable subscriptions?

There’s still debate on what drives App Store rankings, but some confirmed factors include app name, subtitle, keyword field, downloads, ratings, and in-app events. Likely influences are stability, retention, conversion rate, and user behavior. Search relies most on metadata, Top Charts focus on download velocity, and Featured spots are editorially chosen. Elements like promo text, long description, and release notes don’t impact rankings.

I’m trying to clarify keyword usage in App Store Optimization. Apple’s docs suggest you can use phrases like “Near Me” instead of separating words with commas (“Near,Me”). Does assigning phrases directly improve ranking compared to letting Apple combine single keywords?

I want that the user can watch a short clip in the App Store before the user decides to download my game in the App Store. I want to upload a clip to App Store Connect but I don't know how to do that. And I get this warning: To provide metadata for your app clip, you must first upload a build to App Store Connect that contains a clip. Is it necessary that the user can watch the clip in my game or should the video file just be included in the build even if the clip cannot be watched in my game? Is it necessary to upload the clip first to YouTube and then paste the URL in App Store Connect?

In App Store Connect I can add up to 10 images for each iPhone/iPad display. But I don't know which resolution is the best for my screenshots in the App Store and I don't know if the screenshots could be displayed distorted if I don't upload png images for each iPhone/iPad display in App Store Connect. Should I upload for each iPhone/iPad display up to 10 screenshots in the highest possible resolution? For example, for the iPhone 6.5" display it would be 1284 × 2778px or 2778 × 1284px.

As the title says, I am enrolled in the small business program but Apple still takes about 30% of my sales. Most of my sales are from Swedish customers, not sure if this matters. For instance I have an app with sales of: $109 After apples cut I am left with: $74 74/109 = 0.68. Why is this? I have non consumable IAP in my app.

I want to publish my game next year in the Apple App Store but I want to choose the time period manually. Can I upload my game for app review without releasing it automatically afterwards? Where exactly can I choose in App Store Connect if my game is published automatically or manually after the app review process? Currently I only use TestFlight.

Hi, Some time ago I created an Apple Developer business account on behalf of my (now former) business partner. The company is no longer active, and I've been away from app development for a few years. I'd now like to start fresh with a new business account, but first I need to step away from this existing one. From the documentation, I understand that first I have to transfer the Account Holder role, and I've already spoken with the other person - he's willing to accept the role. According to the docs: https://developer.apple.com/help/account/access/transfer-the-account-holder-role/ the option should appear under "Update your information", but in my case there is no option called "Transfer Account Holder role". Has anyone encountered this before? Are there prerequisites or account conditions that need to be met for the transfer option to appear? Thanks in advance for any guidance.

Hello, My app uses auto-renewable subscriptions. I submitted an update and at first the subscription products appeared properly under the monetization section in App Store Connect. However, after resubmitting the binary for review, the subscription product attachment disappeared, and now it is not possible to re-attach them. Even sandbox testing cannot retrieve the subscription identifiers anymore, because the monetization section no longer shows the products. Questions: Why did the subscription products disappear after a resubmission? How can I re-attach subscription products to the new version? Do I need to remove the current version submission to make subscriptions appear again? Does App Review need to finish processing subscription approval separately? Notes: The first version binary showed subscription products. After internal rejection and resubmission, they disappeared. Using StoreKit 2 restore flow in production code. Sandbox accounts cannot fetch product identifiers. Any guidance would be appreciated. Thanks.

Hello guys I’m unable to delete the Test Information and Beta App Information sections on Apple Store Connect. I need to remove them because the app transfer process requires it. I’ve already expired all builds, removed all testers and groups, and tried every possible solution I could find online, but nothing worked. I also contacted Apple Support, but the issue hasn’t been resolved. What should I do next?

应用ID(id6754838125), A week has passed since I added in-app purchases to the already listed application, but it's still under review and I haven't received any result. I sent an email to inquire and asked me to keep waiting We used Contacts Us There is no result. 2. The call has been made for expedited review. It was submitted on December 11th and is still under review Previously, the result of the app review was available within 48 hours Now, I don't know what solutions can be made to this problem. The company is in a hurry and needs to use the App to release a new movie

Two hours ago we received 42 emails from Apple with the following content: iTunes Connect Dear ....., The routing number you provided for the bank account ending in ..... is no longer correct. To receive payments, update your bank info with a valid account and routing number. If you have any questions, use the Contact Us module on iTunes Connect. We have been receiving payments to this account for 5 years and nothing has changed with the account. The account is valid and all details are correct. And this is displayed under “Payments and Financial Reports”: Payment Rejected The routing number you provided for the bank account ending in .... is no longer correct. To receive payments, update your bank info with a valid account and routing number. A lovely surprise for Christmas.

Hello everyone, I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review. Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic. Some relevant context: The app is built with Flutter using a single shared codebase. The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues. The iOS version, using that same implementation, continues to receive 4.3(a) rejections. We do not use purchased templates and do not operate multiple developer accounts. Like most apps, we use some third-party and open-source components where technically appropriate. Across multiple submissions, we have tried to address the feedback as best we can by making changes to UI/UX, assets, metadata, internal structure, and overall product quality. However, App Review has not provided clarification even at a high level (for example, whether the concern is primarily related to UI/UX, code structure, metadata, user flows, or overall product framing). Requests for any directional guidance have resulted in the same generic responses, both in review replies and via support. This leaves us making blind changes without a feedback loop. As a result, it’s difficult to understand whether the issue is realistically correctable, or whether the app is effectively blocked due to similarity clustering or other non-obvious review heuristics. Any firsthand experiences, practical steps, or lessons learned would be extremely helpful.

Xcode 26.2 RC has been out for over 24 hours and it's still not possible to submit apps.

Here are some tips from App Review for a smooth review experience. We’ve split them into two categories: Before You Submit and After You Submit. We’ve also made an easy-to-follow Submission Guide you can save and reference at any point on your App Store journey. Before You Submit Tips Enable a complete review. Make sure you’ve provided demo accounts or implemented an account demonstration mode before you submit. We’ll need to review the entire app experience, both with and without an account. Provide up-to-date demo account login credentials in the App Review Information section on the app version page in App Store Connect. If your app has multiple account types (such as admin and general users), use the Notes field to provide additional demo account credentials for each account type. If your app requires an authentication code in addition to the login credentials, provide the code in advance in the Notes field. Otherwise, a call may be required to complete the review. Apps that handle sensitive user information, or operate in highly regulated industries, can implement demonstration modes that exhibit full features and functionality while using demonstration data. Use the Notes field in App Store Connect to provide information to App Review. The App Review Information section of App Store Connect includes a Notes field. Provide any information that could be relevant to your submission’s review: Submitting a new app? Tell us about your app's concept, business model, and if your app is designed to only operate in certain locations. Submitting an update? Tell us about what’s changed and where to locate significant new content or features. Connecting to hardware? Attach a video, not a screen recording, that shows both the hardware and the app running on a physical Apple device as they pair and interact. Test your app on physical devices before submitting for review. Use TestFlight to distribute your app for beta testing. App Review evaluates apps the way your users will use them: installed on real devices and connected to networks with real-world conditions. Make sure your pre-submission testing includes running the app on each device platform where it could be used. Users expect the app to function on all the devices where it’s available. TestFlight will help you do quality assurance and beta testing on real devices. Share your beta app with internal testers on your Apple Developer Program account or to external users via an email invite or public link. Configure In-App Purchases for review in the sandbox environment. App Review assesses In-App Purchases in the same sandbox environment Apple provides for testing them. The sandbox lets us use real product data and server-to-server transactions, without incurring any financial charges. Take these steps to prepare your In-App Purchases for review: Accept the Paid Applications Agreement in App Store Connect. Submit the In-App Purchases in App Store Connect that you’d like reviewed. Follow the steps in TN3186: Troubleshooting In-App Purchases availability in the sandbox if your app fails to display your In-App Purchases. Note: In-App Purchases don’t need prior approval from App Review to function in review. Join a Meet with Apple event if you need assistance before you submit for review. Request an App Review appointment through Meet with Apple to chat with an App Review expert about how to prepare for review, ask questions about specific guidelines, and discuss other topics related to the review process. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays. After You Submit Tips Contact App Review if you need assistance with an ongoing submission. If your submission doesn’t pass review and you have questions, contact App Review directly by clicking Reply to App Review in App Store Connect. You’ll receive a reply from a review specialist who’s familiar with your app. You can also use the Reply to App Review message window to request a call with an Apple representative. Include your preferred time and language for the call and we’ll do our best to accommodate your requests. Use the Bug Fix Submissions process to quickly deliver bug fixes and resolve other issues on the next submission. If an update includes bug fixes and is rejected, you will be given the option to resolve the issues on your next submission, as long as there are no legal or safety concerns. App Review will let you know if your submission is eligible by including this note at the top of the rejection message: Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. To accept this offer, simply reply to the rejection message in App Store Connect and let App Review know you’ll resolve the issues on the next submission. Share ideas with Apple about how to improve or clarify the App Review Guidelines by submitting guideline feedback. Just as the App Store is always changing and improving to keep up with the needs of customers, the App Review Guidelines may be revised to provide new and updated guidance. If you have ideas for improving or clarifying our requirements you can suggest guideline changes. If your submission was rejected but you believe it follows the App Review Guidelines, consider submitting an appeal to the App Review Board. If your submission didn’t pass review but you have reason to believe it follows the App Review Guidelines, you can submit an appeal to the App Review Board. You can also file an appeal if you think we misunderstood your app or the review was unfair. The App Review Board will contact you as soon as they complete their investigation.

I am the sole Account Holder for my Apple Developer Program account and am encountering an issue where the acceptance of the updated Apple Developer Program License Agreement is not syncing correctly between the two developer portals. Issue Details: Agreement Status on developer.apple.com: I successfully accepted and reviewed the updated agreement at https://developer.apple.com/account. The Agreements section confirms the acceptance date as December 11, 2025 (as seen in the attached image). Status on App Store Connect: Despite this confirmation, when I sign into https://appstoreconnect.apple.com/, I still see the following critical warning: "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." Impact: This prevents me from performing key tasks, such as creating a new app, which triggers an "Agreement Update" alert that only directs me back to the already-accepted agreement on the Developer website. Troubleshooting Steps Taken: I confirmed I am logged in as the Account Holder. I cleared my browser cache and attempted the process on a fresh browser session. My macOS is fully up to date. I have already contacted Apple Developer Support but have not yet received a reply. Request for Assistance This is blocking my ability to submit and update apps. I am aware that direct phone support is often recommended for these issues, but my country is not listed for phone extension support. Has anyone else experienced this sync delay or found a workaround that resolves the "Agreement Update" alert on App Store Connect when the agreement has been accepted on the Developer website? Any advice on the next immediate steps I should take while waiting for my support ticket to be processed would be greatly appreciated.

I am implementing In App Purchase and integrating App Store Server Notifications version 2. I am able to receive the JWSSignedPayload from Apple. The payload is Base64 encoded and contains header, payload, and signature. The documentation clearly explains how to decode the payload and extract claims such as notificationType and data. What is unclear is how to verify the JWS signature itself. I could not find concrete documentation that explains: Which Apple public key or certificate should be used for verification How to retrieve or rotate the key used to sign the payload The exact steps required to validate the JWS signature before trusting the payload Signature verification is critical for security, and simply decoding the claims without validation is not sufficient. I am looking for official guidance or a recommended approach to verify the JWSSignedPayload signature for App Store Server Notifications v2.