Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: "The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise." The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep receiving the exact same copy-pasted template response. It feels like a human is not actually reading the appeals. My Questions: How can I escalate this past the initial review tier to someone who can read the context? Has anyone else experienced being rejected for copying themselves? What specific "documentary evidence" does App Review usually want in this scenario to prove I own my own name? Would my domain registration receipt for linkwise.app be sufficient, or do they require formal trademark documentation? Any advice on how to get this in front of a real person would be greatly appreciated. Thank you!

Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.storekit.external-purchase-link = YES The Provisioning Profile also contains both entitlements (confirmed via codesign -d --entitlements :-). 📄 3. Info.plist Configuration Both keys are configured with correct region codes according to documentation: SKExternalPurchase SKExternalPurchaseCustomLinkRegions 🌍 4. Test Storefront Device storefront verified as United States (US) or Portugal (PT) (US = target region for External Purchase Link, PT = EU region) But despite all the above configuration, both API calls consistently return false: ExternalPurchaseLink.canOpen // false ExternalPurchaseCustomLink.isEligible // false So I cannot proceed to testing the remaining flow (token retrieval, link opening, etc.) ------ Questions ------ ❓ Q1) Local Development Build Limitation Is it expected behavior that Developer-signed local builds always return canOpen = false / isEligible = false for External Purchase Link & Custom Link? Is there a technical or policy restriction that prevents eligibility in local dev builds? ❓ Q2) App Store Connect Configuration Requirement Are there mandatory App Store Connect settings (such as external purchase URLs, support URL, disclosures, or country configuration) that must be enabled before eligibility becomes true? Currently, no External Purchase Link or Custom Link menu is visible in my App Store Connect app settings. Is this menu only available after certain approvals or under specific conditions? ❓ Q3) TestFlight Requirement Do External Purchase Link and Custom Link only return eligibility = true on: TestFlight builds, or Distribution-signed builds? Or should eligibility also work on developer builds? Formal confirmation would be helpful. ❓ Q4) Developer Account Type Limitation We are using an Individual Developer Account (not Organization). Can Individual accounts fully request, test, and ship apps using: External Purchase Link External Purchase Custom Link Or are there limitations on account type? 🙏 Request We have completed all documented setup steps (Entitlements → Provisioning → Info.plist), but eligibility remains false, blocking feature validation. Please clarify which of the following is the cause: Local development builds do not support eligibility Missing App Store Connect configuration (not visible to us) Account type restriction Region rollout or entitlement approval requirement Any additional setup not documented publicly Thank you for your assistance.

In App Store Connect I've uploaded a new build about 11 hours ago and but I'm unable to distribute the App to my tester groups - including internal. The internal group is grayed out. I am able to Select an External group but they actually do not receive any email notification nor do they see any update within their TestFlight App. I've attempted to upload the build a few times, including old builds which had been distributed in the past to no avail. I'm not able to distribute to any tester group, please advise.

I have an app for iOS already on the AppStore and I'm trying to add a macOS version of it. The AppID prefix for this app is different than my Team ID. This mismatch was always fine for submitting my iOS app. However for some reason, the macOS version gets rejected when I upload it. It tells me the AppID prefix must match my Team ID. I do not control my TeamID and I do not control my AppID prefix, they are both given to me by Apple. Yet the error message tells me they must match. How do I get past this? Here is the error message: Validation failed Invalid code signing entitlements. Your application bundle's signature contains code signing entitlements that aren't supported on macOS. Specifically, the "APPID_PREFIX.MY_BUNDLE_ID" value for the com.apple.application-identifier key in "MY_PACKAGE" isn't supported. This value should be a string that starts with your Team ID, followed by a dot ('"), followed by the bundle ID. (ID: 930b77ae-099f-4798-a14a-2803f2a9be9e) Thanks in advance for any pointer.

Hello, I submitted my app for review several days ago, but the status is still “Waiting for Review.” It appears that nobody from the Apple review team has started reviewing the app yet. This situation is extremely frustrating and unacceptable for developers who depend on timely reviews to maintain and release their applications. Waiting days, weeks, or even a month just to receive a potential rejection due to a fixable issue wastes a significant amount of time for development teams. The main problem is not only the delay itself, but the lack of progress. The status remains stuck at "Waiting for Review", which suggests that the review process has not even begun. I have also noticed that many other developers are currently experiencing the same issue, which suggests that this may be a broader problem affecting the App Store review system. Could someone from Apple please clarify: Why apps are staying in “Waiting for Review” for so long Whether there is currently a backlog or system issue affecting reviews What developers can do to avoid these long delays At this point, I would really appreciate an immediate solution or at least an explanation for what is happening with the review process. SUBMISSION ID: c56590cd-cbdb-429d-9555-163efabda47b Thank you.

Hello, I am trying to understand what is happening with my submissions because the situation has become very unusual. I currently have three applications in the App Store review queue: • Healthoria – submitted Feb 5, 7:01 PM • OrbitGoals – submitted Feb 17, 4:11 PM • Memochron – submitted Mar 10 All three of them are still in “Waiting for Review.” The first submission has now been waiting for over a month. During this time I have sent support emails and submitted an expedited review request, but I have not received any response or update. What makes this situation more confusing is that most developers report review times of 2–3 days. Seeing my apps remain in the queue for weeks without any communication makes it difficult to understand whether there is a technical issue, an account-related delay, or something else affecting the process. I completely understand that review times can vary, but having three separate apps all stuck in the same stage for this long seems highly unusual. If anyone from Apple or other developers have experienced a similar situation, I would greatly appreciate any clarification or guidance. Thank you. Best regards, Berkay

Hello App Review Team and iOS Developer Community, We submitted our iOS application on February 25, and within a few hours its status changed to “In Review.” Shortly after that, we received a call from the App Review team requesting some clarification. We provided the requested information during the call, and the same request was later posted in App Store Connect as an unresolved issue. We responded to the request within an hour, providing all the necessary details. However, since then we have not received any further updates regarding the review status. Because this application is related to upcoming sports events, the timing is quite critical. Our client, who owns the sports rights, had planned a launch event on March 6, but unfortunately it had to be postponed because the iOS app was not yet available on the App Store. The sports events are scheduled to begin next week, and our client is planning a marketing campaign ahead of the events, which depends on the app being available. We have already: Submitted an Expedited Review request Contacted Apple Support twice via email At the moment we are unsure how to proceed, as we expected the review process to be completed within the typical 24 hour timeframe mentioned in Apple’s documentation. Does anyone know if there is any additional way to contact the App Review team or any steps we can take to help move the review forward? If any Apple staff member is able to look into this, we would be happy to provide the App ID or additional details via a private support channel if needed. Thank you for your support.

My account is invited to a team as admin I already accept the invitation but I can't find the team on developer.apple.com, appstoreconnect.apple.com even on XCode. My colleagues also cant find my account on the user and access tab on apple store connect but when he tried to invite me again it throw an error (A user with this email address already exists on this team.) What should I do to fix this?

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

Hello, I am facing a validation error when uploading a macOS app with a Network Extension. The Error: Invalid system extension. The system extension at “[T] TEXT.app/Contents/Library/SystemExtensions/company_name.network-extension.systemextension” resides in an unexpected location. The Problem: Validation fails only when the app's Product Name contains square brackets: [T] TEXT. If I remove the brackets from the Product Name, validation passes. What I've tried: Setting Product Name to TEXT (without brackets) and CFBundleDisplayName to [T] TEXT. Cleaning Derived Data and rebuilding the archive. Verified that the extension is physically located at Contents/Library/SystemExtensions/. It seems the Apple validation tool fails to parse the bundle path correctly when it contains characters like [ or ]. Question: How can I keep the app name with brackets for the user (in System Settings and Menu Bar) while ensuring the Network Extension passes validation? Is there a way to escape these characters or a specific Info.plist configuration to satisfy the validator?"

Hello everyone, I wanted to check whether other developers are currently experiencing unusually long “Waiting for Review” times. Our app Aslan Wealth (App ID: 6755077470) has been stuck in Waiting for Review for quite a while and has never entered the “In Review” stage. Timeline Feb 18, 2026 – Version submitted for review Feb 23 – Contacted Apple Developer Support regarding review status Feb 24 – Received reply that the case was escalated to the review team Mar 3 – Still in Waiting for Review (confirmed by support that the app is still in the queue) Mar 7–11 – Followed up with Developer Support again Mar 12 – Still Waiting for Review So the app has now been waiting for review for more than 3 weeks without ever entering active review. Additional information All agreements are active No messages in Resolution Center Build was not modified after submission App status remains Waiting for Review Questions Has anyone else recently experienced similar multi-week delays in the “Waiting for Review” stage? If so: Did your app eventually move to In Review without changes? Did Apple provide any explanation for the delay? Is there anything developers can do to help move the process forward? Any recent data points or experiences would be really helpful. Thanks in advance.

显示为——构建描述签名错误: 签名证书无效。签名证书；不可用于代码签名。它可能已被吊销或过期。、 目前是在Apple Developer 重新创建证书、生成描述文件了（显示的是有效）；但是下来出来放进打包里就显示证书失效是什么原因？

Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as "You receive this error when the system prompts a person and they decide not to share their age range with your app. ", as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorithm to test given feature for macOS (mock region, mock age, mock source of approval, revoke declared range, etc). Now I get a review with rejection, stating that I don't have age verification mechanisms present in my app. Also I found out that after filling the App Information regarding Age Ratings it spreads to all fresh releases, so even though my newest macOS release doesn't contain age verification mechanisms yet, it should, as iOS release has got this functionality up and running already and I had to check this when filling Age Ratings questionnaire. Now I'm stuck between removing this capability from App Information, so the macOS release can pass and stalling macOS releases until there is a proper usable API to implement Declared Age Range verification properly (at least the same way as on iOS). How should I properly develop and test this feature for macOS before releasing it publicly?

Hi, My app VITTRA has been approved and is live on the App Store. also i have already pushed even another update …However, I submitted two in-app purchases along with the app: 1. VITTRA Pro (Non-Consumable) — Status: “In Review” 2. AI Scan Pack (Consumable) — Status: “Waiting for Review” The app binary was approved and distributed, but the IAPs are still under review. My app’s core functionality depends on these purchases being available to users. A few questions: 1. Is it normal for IAPs to remain in review after the app itself has been approved and distributed? 2. Is there an expected timeline for IAP reviews when submitted alongside a new app? 3. Is there anything I can do to expedite the process, or should I just wait? Any guidance would be appreciated. Its a real frustrating situation and there is not a single response from the support. Thanks!

I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: "Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found" With NSExtensionPrincipalClass → Local install fails with: "defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension" Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key allows upload but breaks local installation. Is this a known issue? Is there a workaround or correct Info.plist configuration for DeviceActivityReportExtension? Thank you!

Hello everyone, I'm currently waiting for my Apple Developer Program enrollment to be approved and wondering if my timeline is normal. My situation: Payment of $99 USD: ✅ Completed (have invoice and order number) Government-issued photo ID: ✅ Submitted Confirmation email received: ✅ Yes - "Thank you for providing the documents we requested. We will review them and follow up with you within two business days" Days since confirmation email: 3+ business days The email stated they would follow up within two business days, but it's now been more than three business days with no update. My questions: Is it normal for the review to take longer than the stated "two business days"? For those who were approved, did you receive multiple emails throughout the process, or just a final approval email? Has anyone experienced similar delays? What was the outcome? Just want to make sure nothing is stuck or requires additional action from my side. Thanks for any insights!

I currently have my own individual App Store Connect and Apple Developer distributor account registered with the email address m*******@*mail.com. For one of my clients, we also created a separate individual App Store Connect and Apple Developer account. I added my account as an Admin to the client’s account. On the App Store Connect side, I can perform all operations without any issues, such as managing the app, handling TestFlight, and submitting new versions. However, when I access the Apple Developer portal, I cannot see or manage the accounts I am responsible for. For example, I cannot view information such as the Team ID, certificates, provisioning profiles, or other developer settings. To work around this issue, I created a new Apple Developer membership using a different email address. However, when I logged in with that account, I was still unable to view the Team ID or other developer-related settings. My question is: Has the system always worked this way, where App Store Connect and Apple Developer access are managed separately? Or could this be an unnoticed authorization or configuration issue? I would appreciate your clarification on this matter.

Hello everyone, I am an iOS developer and both my apps are experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. These are existing apps on app store with simple updates. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. AppleID: 6756242440 and 6746870245 Please help us resolve the issue. Thanks in advance

Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.