App Store Connect

RSS for tag

App Store Connect is a suite of tools for submitting and managing your apps and in-app purchases on the App Store.

Posts under App Store Connect tag

200 Posts

Post

Replies

Boosts

Views

Activity

Invalid Entitlement: Unknown ID
I am attempting to configure appclips, but I am getting this error in App Store Connect. I created an app clips target in my project, I have checked the XCAsset files and it is included when archived and pushed to App Store Connect. In both my parent and my app clips target I've added the associated domains capabilities, with the following associated same domains for both targets: appclips:akin-server-side-staging.onrender.com appclips:akin-server-side.onrender.com applinks:akin-server-side-staging.onrender.com applinks:akin-server-side.onrender.com My server is configured to serve the following json at all permutations of the staging endpoints and prod endpoints for both well known and aasa without well known. Here is one of them: https://akin-server-side.onrender.com/.well-known/apple-app-site-association Here is the JSON it is returning: {"applinks":{"details":[{"appIDs":["8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1"],"components":[{"\/":"\/appClips\/referral\/venueToUser\/*"}]}]},"appclips":{"apps":["8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1.Clip"]}} And yet I'm still getting Invalid Entitlement: Unknown ID in the store.
4
0
191
1w
Advanced App Clip Experiences — Backend Shows PUBLISHED but iOS Returns "App Clip Unavailable" (CDN Propagation Failure)
We have 7 Advanced App Clip Experiences that have been stuck showing "Received" in the App Store Connect UI for 90+ days. However, after inspecting the underlying API response, we can confirm all 7 experiences show "key": "PUBLISHED", "doc_count": 7 on the backend. Despite this, scanning a QR code on a device without the app installed returns "App Clip Unavailable" on every experience. This appears to be a CDN propagation failure — the backend is PUBLISHED but the edge nodes serving iOS devices are returning stale or missing data. Evidence – – App Clip Diagnostics tool shows all green checks for our registered experience URLs (screenshots attached) – App Store Connect UI shows "Received" for all 7 experiences – Backend API response (/appclips/api/v1/experiences) shows: json"statuses": { "buckets": [ { "key": "PUBLISHED", "doc_count": 7 } ] } – iOS devices without the app installed still return "App Clip Unavailable" when scanning QR codes – App version 1.4(6) is live and Ready for Distribution – AASA file is correctly configured and verified – Bundle ID com.goodtrkr.pixlbankar.Clip is correctly associated. Business Impact – This is a production blocker for our AR platform (PixlBank[ar] — Good TRKR LLC). Our entire product delivery depends on App Clip invocation via QR code for enterprise clients. We have been engaged with Apple DTS for 90+ days: TSI Case-ID: 18681098 New Case-ID: 18880040 Feedback Assistant report filed with diagnostic screenshots and sysdiagnose provided no help. REQUEST –  Can an Apple DTS engineer confirm whether there is a known CDN propagation issue affecting App Clip Experiences that are in PUBLISHED state on the backend but not being served correctly to iOS devices? And if so, is there a way to trigger a cache flush or re-propagation for our specific experiences?
0
0
117
1w
Xcode 16 warning about missing symbols of static framework
I work on an SDK, and one of the ways we distribute it is as a pre-compiled static XCFramework. As far as I know, it’s the nature of a static framework to not contain symbols since the framework will be embedded in the final app binary, and the symbols should then be generated. However, when testing the "Validate" function of the Xcode 16 deployment process, our users are receiving a warning that says the framework does not contain symbols. Is my assumption about static frameworks and symbols incorrect? Could this be a bug in Xcode 16? Should we modify something in our framework to inform Xcode that symbols are not needed?
48
24
44k
1w
App stuck in “Waiting for Review” for 10+ days (Case ID: 102845134369)
App Review App Store Connect Hi everyone, My iOS app has been stuck in “Waiting for Review” for over 10 days, and I’m starting to worry there might be an issue with my submission or account. Here are the key timeline details (GMT+7): Feb 3, 2026 – Submitted app → entered Waiting for Review Feb 5, 2026 – App went In Review and was later Rejected by Apple Feb 5 – Mar 2, 2026 – I made fixes and resubmitted Then on Mar 2, 2026: Submitted again → Waiting for Review On Mar 8, 2026: I made several quick re-submissions (Developer Rejected → Ready for Review → Waiting for Review multiple times within minutes) Since then: Mar 8, 2026 → Today (Mar 18, 2026) Status has remained “Waiting for Review” with no progress I have already contacted Apple Developer Support: Case ID: 102845134369 However, I haven’t received any meaningful update yet. My concerns: My app was previously reviewed (reached In Review and got feedback), so it doesn’t seem like a completely new or blocked app. The app itself is relatively simple (no sensitive content, no unusual permissions). I did perform multiple rapid re-submissions on Mar 8 — I’m not sure if that might have affected the review queue. My questions: Could multiple rapid “Developer Rejected → Resubmitted” actions cause my app to be deprioritized or delayed in the review queue? Is it normal for an app to stay in “Waiting for Review” for 10+ days without any status change? Should I: Keep waiting, or Cancel and resubmit again, or Submit a new build version? Is there any way to verify if my app/account has been flagged or requires additional information that is not shown in App Store Connect? I understand that review times can vary, but this feels longer than usual, especially since there has been no transition to In Review. If anyone (or Apple staff) has experienced something similar or has advice on how to proceed, I would really appreciate your guidance. Thank you very much.
1
0
45
1w
App stuck in “Waiting for Review” for 10+ days (Case ID: 102845134369)
App Review App Store Connect Hi everyone, My iOS app has been stuck in “Waiting for Review” for over 10 days, and I’m starting to worry there might be an issue with my submission or account. Here are the key timeline details (GMT+7): Feb 3, 2026 – Submitted app → entered Waiting for Review Feb 5, 2026 – App went In Review and was later Rejected by Apple Feb 5 – Mar 2, 2026 – I made fixes and resubmitted Then on Mar 2, 2026: Submitted again → Waiting for Review On Mar 8, 2026: I made several quick re-submissions (Developer Rejected → Ready for Review → Waiting for Review multiple times within minutes) Since then: Mar 8, 2026 → Today (Mar 18, 2026) Status has remained “Waiting for Review” with no progress I have already contacted Apple Developer Support: Case ID: 102845134369 However, I haven’t received any meaningful update yet. My concerns: My app was previously reviewed (reached In Review and got feedback), so it doesn’t seem like a completely new or blocked app. The app itself is relatively simple (no sensitive content, no unusual permissions). I did perform multiple rapid re-submissions on Mar 8 — I’m not sure if that might have affected the review queue. My questions: Could multiple rapid “Developer Rejected → Resubmitted” actions cause my app to be deprioritized or delayed in the review queue? Is it normal for an app to stay in “Waiting for Review” for 10+ days without any status change? Should I: Keep waiting, or Cancel and resubmit again, or Submit a new build version? Is there any way to verify if my app/account has been flagged or requires additional information that is not shown in App Store Connect? I understand that review times can vary, but this feels longer than usual, especially since there has been no transition to In Review. If anyone (or Apple staff) has experienced something similar or has advice on how to proceed, I would really appreciate your guidance. Thank you very much.
1
0
90
1w
App Approved And Again Subscription - "Waiting For Review"
Another Limbo with IAP. I'm genuinely baffled by this. My app " Tapix - AI Writing Keyboard " was reviewed, approved, and is currently live and downloadable on the App Store. Great except the auto-renewable subscription that I submitted at the same time is STILL sitting in "Waiting for Review." Let me spell out what this means for real users: A user finds my app on the App Store They download it They open it and hit the subscription screen Nothing works. They can't subscribe. The core functionality is locked behind a paywall that Apple hasn't approved yet. They think the app is broken They leave a 1-star review and delete it. This is an absolutely terrible first impression and there's nothing I can do about it from my side. Everything is configured correctly metadata, pricing, review screenshots, subscription group, product IDs all of it. The app was approved. The subscription just... wasn't. How is it possible that Apple approves and distributes an app but leaves the IAP that the app literally depends on in limbo? Shouldn't these be reviewed together? Why would you release an app to users in a state where its core monetization is non-functional? Every hour this sits in "Waiting for Review" is real damage and a launch that's essentially sabotaged through no fault of my own. I'm asking for any guidance on how to escalate this. This needs urgent attention. Thank you. App Name - Tapix AI Keyboard
1
0
83
2w
What’s the recommended approach for using (or avoiding) special characters in the App Store keyword metadata?
I am submitting an app to the App Store and want to understand the best way to handle keywords that include special characters. If a keyword has accents like coração and users may search for coracao without accents, should I include both versions or rely on Apple to match them automatically?
2
1
120
2w
Curious about the shift from iOS developer to full time indie developer Ask Me Anything 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
1
0
48
2w
Expedited Review Granted but Apps Stuck in "Waiting for Review" for 12 Days (Case ID: 102840953234)
Hello Apple Developer Community and App Review Team, I am reaching out here because I am completely stuck and have not received a response from the standard support channels. On March 4th, I requested and was successfully granted an Expedited Review for a critical bug fix for two of my apps ("Who Wants to Be AI Professor?" and "The Fed Chair"). However, it has been 12 days and both apps are still stuck in the "Waiting for Review" status. Suspecting a system glitch or "ghosting" issue, I contacted App Store Connect support on March 10th and received Case ID: 102840953234. The automated email stated I would receive a reply within 2 business days, but that time has long passed with no response. I kindly ask if an App Review Team member or Apple Staff could look into this Case ID and check if my submissions are stuck in a technical loop. I have refrained from canceling and resubmitting to avoid further delays, but I am currently completely blocked. Any help to push these manually to the review desk would be immensely appreciated. Thank you!
1
0
71
2w
How can I provide free test accounts for mobile games reviewers?
I want to provide free test accounts so that mobile games reviewers can play my iOS game for free. They should be able to make in-app purchases(consumables) without any charges. I don´t know how to create the free test accounts. Is it necessary that my iOS game is already published in the Apple App Store before I can provide test accounts for mobile games reviewers? Or is it necessary to let the reviewers play my game while it is still in TestFlight? If yes, should I ask them to give me there email address so that I can add it to my Sandbox accounts? My game was not yet released in the App Apple Store. It´s only available on TestFlight.
0
0
56
2w
App stuck in "Waiting for Review" for over two weeks
Hello, I submitted my app for review for the first time about two weeks ago and it is still stuck in "Waiting for Review" with no update. I haven't received any feedback yet and I'm not sure if this kind of delay is normal or if something might be wrong. Has anyone experienced something similar? What did you do in this situation? Thanks.
2
1
155
2w
App Still “Waiting for Review” Since Feb 2 – Is This Normal?
Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.
2
0
175
2w
Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
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
4
0
139
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
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!
2
0
93
2w
Unable to enable eligibility for External Purchase Link APIs — seeking clarification
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.
2
1
237
2w
Unable to Add Internal Groups to TestFlight Builds / Cannot distribute
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.
9
5
10k
2w
Team ID and App ID prefix mismatch for macOS
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.
1
0
76
2w
Invalid Entitlement: Unknown ID
I am attempting to configure appclips, but I am getting this error in App Store Connect. I created an app clips target in my project, I have checked the XCAsset files and it is included when archived and pushed to App Store Connect. In both my parent and my app clips target I've added the associated domains capabilities, with the following associated same domains for both targets: appclips:akin-server-side-staging.onrender.com appclips:akin-server-side.onrender.com applinks:akin-server-side-staging.onrender.com applinks:akin-server-side.onrender.com My server is configured to serve the following json at all permutations of the staging endpoints and prod endpoints for both well known and aasa without well known. Here is one of them: https://akin-server-side.onrender.com/.well-known/apple-app-site-association Here is the JSON it is returning: {"applinks":{"details":[{"appIDs":["8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1"],"components":[{"\/":"\/appClips\/referral\/venueToUser\/*"}]}]},"appclips":{"apps":["8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1.Clip"]}} And yet I'm still getting Invalid Entitlement: Unknown ID in the store.
Replies
4
Boosts
0
Views
191
Activity
1w
Advanced App Clip Experiences — Backend Shows PUBLISHED but iOS Returns "App Clip Unavailable" (CDN Propagation Failure)
We have 7 Advanced App Clip Experiences that have been stuck showing "Received" in the App Store Connect UI for 90+ days. However, after inspecting the underlying API response, we can confirm all 7 experiences show "key": "PUBLISHED", "doc_count": 7 on the backend. Despite this, scanning a QR code on a device without the app installed returns "App Clip Unavailable" on every experience. This appears to be a CDN propagation failure — the backend is PUBLISHED but the edge nodes serving iOS devices are returning stale or missing data. Evidence – – App Clip Diagnostics tool shows all green checks for our registered experience URLs (screenshots attached) – App Store Connect UI shows "Received" for all 7 experiences – Backend API response (/appclips/api/v1/experiences) shows: json"statuses": { "buckets": [ { "key": "PUBLISHED", "doc_count": 7 } ] } – iOS devices without the app installed still return "App Clip Unavailable" when scanning QR codes – App version 1.4(6) is live and Ready for Distribution – AASA file is correctly configured and verified – Bundle ID com.goodtrkr.pixlbankar.Clip is correctly associated. Business Impact – This is a production blocker for our AR platform (PixlBank[ar] — Good TRKR LLC). Our entire product delivery depends on App Clip invocation via QR code for enterprise clients. We have been engaged with Apple DTS for 90+ days: TSI Case-ID: 18681098 New Case-ID: 18880040 Feedback Assistant report filed with diagnostic screenshots and sysdiagnose provided no help. REQUEST –  Can an Apple DTS engineer confirm whether there is a known CDN propagation issue affecting App Clip Experiences that are in PUBLISHED state on the backend but not being served correctly to iOS devices? And if so, is there a way to trigger a cache flush or re-propagation for our specific experiences?
Replies
0
Boosts
0
Views
117
Activity
1w
Xcode 16 warning about missing symbols of static framework
I work on an SDK, and one of the ways we distribute it is as a pre-compiled static XCFramework. As far as I know, it’s the nature of a static framework to not contain symbols since the framework will be embedded in the final app binary, and the symbols should then be generated. However, when testing the "Validate" function of the Xcode 16 deployment process, our users are receiving a warning that says the framework does not contain symbols. Is my assumption about static frameworks and symbols incorrect? Could this be a bug in Xcode 16? Should we modify something in our framework to inform Xcode that symbols are not needed?
Replies
48
Boosts
24
Views
44k
Activity
1w
App stuck in “Waiting for Review” for 10+ days (Case ID: 102845134369)
App Review App Store Connect Hi everyone, My iOS app has been stuck in “Waiting for Review” for over 10 days, and I’m starting to worry there might be an issue with my submission or account. Here are the key timeline details (GMT+7): Feb 3, 2026 – Submitted app → entered Waiting for Review Feb 5, 2026 – App went In Review and was later Rejected by Apple Feb 5 – Mar 2, 2026 – I made fixes and resubmitted Then on Mar 2, 2026: Submitted again → Waiting for Review On Mar 8, 2026: I made several quick re-submissions (Developer Rejected → Ready for Review → Waiting for Review multiple times within minutes) Since then: Mar 8, 2026 → Today (Mar 18, 2026) Status has remained “Waiting for Review” with no progress I have already contacted Apple Developer Support: Case ID: 102845134369 However, I haven’t received any meaningful update yet. My concerns: My app was previously reviewed (reached In Review and got feedback), so it doesn’t seem like a completely new or blocked app. The app itself is relatively simple (no sensitive content, no unusual permissions). I did perform multiple rapid re-submissions on Mar 8 — I’m not sure if that might have affected the review queue. My questions: Could multiple rapid “Developer Rejected → Resubmitted” actions cause my app to be deprioritized or delayed in the review queue? Is it normal for an app to stay in “Waiting for Review” for 10+ days without any status change? Should I: Keep waiting, or Cancel and resubmit again, or Submit a new build version? Is there any way to verify if my app/account has been flagged or requires additional information that is not shown in App Store Connect? I understand that review times can vary, but this feels longer than usual, especially since there has been no transition to In Review. If anyone (or Apple staff) has experienced something similar or has advice on how to proceed, I would really appreciate your guidance. Thank you very much.
Replies
1
Boosts
0
Views
45
Activity
1w
Enrollment
Celebrating exactly 6 weeks since I purchased the Apple Developer account, and it still hasn’t been approved🙂🎂
Replies
1
Boosts
0
Views
70
Activity
1w
App stuck in “Waiting for Review” for 10+ days (Case ID: 102845134369)
App Review App Store Connect Hi everyone, My iOS app has been stuck in “Waiting for Review” for over 10 days, and I’m starting to worry there might be an issue with my submission or account. Here are the key timeline details (GMT+7): Feb 3, 2026 – Submitted app → entered Waiting for Review Feb 5, 2026 – App went In Review and was later Rejected by Apple Feb 5 – Mar 2, 2026 – I made fixes and resubmitted Then on Mar 2, 2026: Submitted again → Waiting for Review On Mar 8, 2026: I made several quick re-submissions (Developer Rejected → Ready for Review → Waiting for Review multiple times within minutes) Since then: Mar 8, 2026 → Today (Mar 18, 2026) Status has remained “Waiting for Review” with no progress I have already contacted Apple Developer Support: Case ID: 102845134369 However, I haven’t received any meaningful update yet. My concerns: My app was previously reviewed (reached In Review and got feedback), so it doesn’t seem like a completely new or blocked app. The app itself is relatively simple (no sensitive content, no unusual permissions). I did perform multiple rapid re-submissions on Mar 8 — I’m not sure if that might have affected the review queue. My questions: Could multiple rapid “Developer Rejected → Resubmitted” actions cause my app to be deprioritized or delayed in the review queue? Is it normal for an app to stay in “Waiting for Review” for 10+ days without any status change? Should I: Keep waiting, or Cancel and resubmit again, or Submit a new build version? Is there any way to verify if my app/account has been flagged or requires additional information that is not shown in App Store Connect? I understand that review times can vary, but this feels longer than usual, especially since there has been no transition to In Review. If anyone (or Apple staff) has experienced something similar or has advice on how to proceed, I would really appreciate your guidance. Thank you very much.
Replies
1
Boosts
0
Views
90
Activity
1w
App Approved And Again Subscription - "Waiting For Review"
Another Limbo with IAP. I'm genuinely baffled by this. My app " Tapix - AI Writing Keyboard " was reviewed, approved, and is currently live and downloadable on the App Store. Great except the auto-renewable subscription that I submitted at the same time is STILL sitting in "Waiting for Review." Let me spell out what this means for real users: A user finds my app on the App Store They download it They open it and hit the subscription screen Nothing works. They can't subscribe. The core functionality is locked behind a paywall that Apple hasn't approved yet. They think the app is broken They leave a 1-star review and delete it. This is an absolutely terrible first impression and there's nothing I can do about it from my side. Everything is configured correctly metadata, pricing, review screenshots, subscription group, product IDs all of it. The app was approved. The subscription just... wasn't. How is it possible that Apple approves and distributes an app but leaves the IAP that the app literally depends on in limbo? Shouldn't these be reviewed together? Why would you release an app to users in a state where its core monetization is non-functional? Every hour this sits in "Waiting for Review" is real damage and a launch that's essentially sabotaged through no fault of my own. I'm asking for any guidance on how to escalate this. This needs urgent attention. Thank you. App Name - Tapix AI Keyboard
Replies
1
Boosts
0
Views
83
Activity
2w
What’s the recommended approach for using (or avoiding) special characters in the App Store keyword metadata?
I am submitting an app to the App Store and want to understand the best way to handle keywords that include special characters. If a keyword has accents like coração and users may search for coracao without accents, should I include both versions or rely on Apple to match them automatically?
Replies
2
Boosts
1
Views
120
Activity
2w
Curious about the shift from iOS developer to full time indie developer Ask Me Anything 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
Replies
1
Boosts
0
Views
48
Activity
2w
Promo code generation hanging
Is anyone else having trouble generating App Store promo codes? The promo codes page in App Store Connect is mostly failing to finish loading, and even when it does finish, promo code generation gets stuck on Generating.
Replies
2
Boosts
0
Views
50
Activity
2w
Expedited Review Granted but Apps Stuck in "Waiting for Review" for 12 Days (Case ID: 102840953234)
Hello Apple Developer Community and App Review Team, I am reaching out here because I am completely stuck and have not received a response from the standard support channels. On March 4th, I requested and was successfully granted an Expedited Review for a critical bug fix for two of my apps ("Who Wants to Be AI Professor?" and "The Fed Chair"). However, it has been 12 days and both apps are still stuck in the "Waiting for Review" status. Suspecting a system glitch or "ghosting" issue, I contacted App Store Connect support on March 10th and received Case ID: 102840953234. The automated email stated I would receive a reply within 2 business days, but that time has long passed with no response. I kindly ask if an App Review Team member or Apple Staff could look into this Case ID and check if my submissions are stuck in a technical loop. I have refrained from canceling and resubmitting to avoid further delays, but I am currently completely blocked. Any help to push these manually to the review desk would be immensely appreciated. Thank you!
Replies
1
Boosts
0
Views
71
Activity
2w
How can I provide free test accounts for mobile games reviewers?
I want to provide free test accounts so that mobile games reviewers can play my iOS game for free. They should be able to make in-app purchases(consumables) without any charges. I don´t know how to create the free test accounts. Is it necessary that my iOS game is already published in the Apple App Store before I can provide test accounts for mobile games reviewers? Or is it necessary to let the reviewers play my game while it is still in TestFlight? If yes, should I ask them to give me there email address so that I can add it to my Sandbox accounts? My game was not yet released in the App Apple Store. It´s only available on TestFlight.
Replies
0
Boosts
0
Views
56
Activity
2w
My App e18f049f-bff9-4993-97b4-742c6ba63d0e is stuck in review for longer than usual
Hi, My app wich shipping ID is e18f049f-bff9-4993-97b4-742c6ba63d0e is waiting for review since last month. if there is any place that I can submit a ticket or ask more properly please let me know. best, David Silva
Replies
4
Boosts
0
Views
127
Activity
2w
App stuck in "Waiting for Review" for over two weeks
Hello, I submitted my app for review for the first time about two weeks ago and it is still stuck in "Waiting for Review" with no update. I haven't received any feedback yet and I'm not sure if this kind of delay is normal or if something might be wrong. Has anyone experienced something similar? What did you do in this situation? Thanks.
Replies
2
Boosts
1
Views
155
Activity
2w
App Still “Waiting for Review” Since Feb 2 – Is This Normal?
Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.
Replies
2
Boosts
0
Views
175
Activity
2w
Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
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
Replies
4
Boosts
0
Views
139
Activity
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
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!
Replies
2
Boosts
0
Views
93
Activity
2w
Unable to enable eligibility for External Purchase Link APIs — seeking clarification
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.
Replies
2
Boosts
1
Views
237
Activity
2w
Unable to Add Internal Groups to TestFlight Builds / Cannot distribute
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.
Replies
9
Boosts
5
Views
10k
Activity
2w
Team ID and App ID prefix mismatch for macOS
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.
Replies
1
Boosts
0
Views
76
Activity
2w