Overview

I currently have multiple macOS app icons configured in my project: AppIcon.icon AppIcon-Development.icon AppIcon-Beta.icon In Xcode, I can assign different app icons for Debug and Release configurations, which works well for local development and production builds. However, I cannot find any equivalent way to specify a dedicated app icon for TestFlight distributions. I would like TestFlight builds to automatically use AppIcon-Beta.icon. Where is this configured, or what is the recommended approach? Is there a specific build setting, archive configuration or App Store Connect mechanism for this, or do I need to handle it manually using build configurations or schemes? Thanks.

Hi, we're urgently trying to resolve the changing of our account membership details. We need our app developer name to match our business name as it's currently wrong. All the information can be found under the case number 102893432961. Could this please be urgently looked into?

Hello Apple App Review Team, I am writing to urgently request your assistance. We have a strict, immovable launch deadline for our app on June 4. We initially submitted the app for review on May 15 and waited for 6 days without any response. Believing something might have gone wrong with the submission system, we self-rejected the binary, made a minor update, and resubmitted it on May 21. The app is currently still stuck in the "Waiting for Review" status. This launch is utterly important to us, and we absolutely cannot miss this deadline. If there is any additional information, documentation, or action required on our end to help expedite this process, please let me know immediately. Thank you very much for your time and support. Best regards, Pattaragorn (Phi) Xian Chiang

Title: MoneyMatters on FIRE — update stuck in review, requesting visibility Hello App Review team, I'm respectfully requesting any visibility into the status of an app update that has shown no movement in the review queue. App: MoneyMatters on FIRE Apple ID (App ID): 6756042174 Platform: iOS Bundle ID : com.shailendra.moneymattersonfire Version / Build: 4.0 (7) Status: Waiting for Review Submitted: 22-05-2026 This is an update to an already-approved, live app. The new version introduces a redesigned, more advanced UI and a new backup-and-restore mechanism for user data. There is no new sensitive functionality. An earlier submission of this same update sat in "Waiting for Review" for roughly 13 days with no status change or Resolution Center messages, which led me to cancel and resubmit. There are no outstanding items in the Resolution Center, no warnings on the account, and all agreements are active. I understand review volumes may be high at the moment, and I'm not requesting an expedited review — I would simply be grateful if someone could confirm whether anything is needed from my side, or whether the submission is still awaiting reviewer assignment. Thank you for your time. thx; Shailendra

I'm a solo developer and fairly new to the App Store process.

Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.

I am implementing device authentication for a macOS app. Our iOS app uses App Attest, but App Attest is not available on macOS, so we are evaluating StoreKit's AppTransaction plus AppStore.deviceVerificationID as the macOS equivalent signal. The issue: in a macOS app installed through TestFlight, AppStore.deviceVerificationID is available, but AppTransaction.shared throws StoreKitError code=2. I reproduced this in a focused standalone macOS test app with no backend and no custom dependencies. Environment: Platform: macOS Distribution: TestFlight App Store Connect app ID: 6769568350 Bundle ID: com.soundcity.AppTransactionProbe App version: 1.0 Build: 1 Observed output from the TestFlight-installed app: Bundle ID: com.soundcity.AppTransactionProbe App version: 1.0 Build: 1 deviceVerificationID available: true deviceVerificationID prefix: CA91ED5D... AppTransaction.shared threw error: StoreKitError; domain=StoreKit.StoreKitError; code=2 The relevant code path is essentially: import StoreKit let deviceVerificationID = try? AppStore.deviceVerificationID let appTransaction = try await AppTransaction.shared In the TestFlight-installed build: AppStore.deviceVerificationID succeeds. AppTransaction.shared throws StoreKitError code=2. Questions: Is AppTransaction.shared expected to work for macOS apps distributed through TestFlight? If yes, what does StoreKitError code=2 indicate in this context, and what setup might be missing? If no, is there an Apple-supported way to obtain an AppTransaction JWS, or equivalent signed App Store/TestFlight app-install assertion, for macOS TestFlight builds? For macOS apps that need a device-bound trust signal comparable to iOS App Attest, is AppStore.deviceVerificationID intended to be used without AppTransaction.shared, or should these APIs be used together? I have a focused Xcode test project that demonstrates the issue and can share it if helpful.

Hello, I'm experiencing a bug on iOS 26.5 RC1/RC2 where the Blood Pressure option is silently excluded from the HealthKit permission dialog (when requesting HKQuantityTypeIdentifierBloodPressureSystolic and HKQuantityTypeIdentifierBloodPressureDiastolic). This does not reproduce on iOS 26.4.2 or earlier. What happens: When BP types are requested alone, a blank white modal slides up and immediately dismisses — no permission UI is shown. When BP is requested alongside other types, a normal dialog appears for those other types, but Blood Pressure is simply absent from the list. The completion handler returns success = YES, error = nil in both cases, but BP permission is never granted. The result: Settings → Privacy & Security → Health → [app] shows Blood Pressure as requested but not granted getRequestStatusForAuthorizationToShareTypes for the BP types keeps returning ShouldRequest indefinitely HealthKit queries for BP samples return no data Workaround: Manually toggling Blood Pressure to ON in Settings → Privacy & Security → Health → [app name] fixes everything - queries work, notifications fire, and getRequestStatusForAuthorizationToShareTypes correctly returns HKAuthorizationRequestStatusUnnecessary. Environment: Confirmed broken: iOS 26.5 RC1 (23F75) and RC2 (23F77), iPhone 11; iOS 26.5 RC1 (23F73), simulator Confirmed working: iOS 26.4.2 (device), iOS 26.4.1 (simulator) Feedback filed as FB22735935.

Hi everyone, I am facing an unusual and prolonged delay with the App Store review process for my app, "ismth水木" (Bundle ID: net.ismth). It has been stuck in the "Waiting for Review" status for 60+ days since my last submission on March 22, 2026. Here is the quick timeline: Feb 20, 2026: First submission. Mar 21, 2026: First rejection received (resolved the issues immediately). Mar 22, 2026: Resubmitted with adjustments. Current Status: Still "Waiting for Review" (has not even changed to "In Review"). I have contacted Developer Support multiple times (Case ID: 102836154889), but I keep receiving the same automated template responses stating that they need more time, with no specific details. Since the vast majority of reviews take less than 48 hours, a 60-day delay without even entering the review stage is highly unusual. I am deeply committed to complying with Apple’s guidelines, but the lack of transparent communication makes it impossible to know if my account is being audited or if there is a technical misunderstanding. Has anyone else experienced a similar "Waiting for Review" bottleneck recently? Any advice on how to escalate this, or any insight from Apple Staff here would be greatly appreciated. Thank you!

Hi everyone, My app “IMAT PREP” (version 1.0) has been stuck in “Waiting for Review” for over a month now without any feedback, rejection, or status change. I’ve already checked: Agreements, tax, and banking Export compliance App metadata and screenshots App Store Connect for any “Action Required” notices Everything appears complete. A few days ago, I requested an expedited review and Apple approved the expedited request, but the app is still waiting for review. This is my first iOS app submission, and the app is educational/test-prep related. Has anyone experienced something similar recently? Is there anything else I should check or do besides waiting/contacting Apple support? Would appreciate any guidance. Thanks!

Hello everyone, I'm facing a very frustrating situation with App Review for my indie app, CoffeePomodoro, and I'm hoping someone here or an Apple engineer can help shed some light on how to escalate and resolve this. My recent update (Version 1.3.1, Submission ID: 59763b52-7c14-4b27-a2cf-2799d2bafe35) was rejected under Guideline 3.1.1 - In-App Purchase. The rejection message states: "We found that the app includes a feature to restore previously purchased In-App Purchase products by entering the user's Apple Account and password. However, In-App Purchases cannot be restored in this manner." The Reality: There is absolutely zero custom UI, form, or TextField in my app that asks for an Apple ID or password. When a user taps "Restore Purchases", the app simply calls Purchases.shared.restorePurchases() via the RevenueCat SDK, which directly wraps Apple's native SKPaymentQueue.restoreCompletedTransactions(). The credential prompt the reviewer saw is the native iOS system-level authentication dialog that appears automatically in the sandbox/TestFlight environment. This usually happens if the device or simulator being used for the review doesn't have an active Sandbox Apple ID already logged in. I have explained this in the App Store Connect Resolution Center. I provided screen recordings showing it's the system dialog, and I attached code snippets proving the app only calls native APIs. Unfortunately, my explanations seem to be ignored, and I keep facing the same roadblock. It feels like the reviewers are mistaking their own OS's native prompt for a custom credential-harvesting screen. Meanwhile, my users are waiting for this update to resolve their subscription issues, and I am stuck in a rejection loop for using Apple's own native API exactly as intended. Has anyone else experienced this specific misunderstanding by the review team? How can I escalate this so someone actually reviews the screen recording and code snippets I provided? Thank you for your time.

My app has been in "Waiting for Review" status since May 8, 2026, and today is May 25, 2026. Before this, I had another submission that was uploaded on April 26, 2026, which also remained pending for a long time. I assumed there may have been an issue on my side, so I removed it and submitted a new build on May 8 — but the new build is still waiting as well.

Hi Team, My app ICY SIM (App ID: 6761278922) has been stuck in "Waiting for Review" for over 4 weeks with no movement, no feedback, and no communication. What I've done: Submitted multiple expedited review requests and resubmissions (I now understand this can reset queue position, so I've stopped doing that) Filed a support ticket 3 days ago (Case ID: 102895038326) — still no response I completely understand the team handles a high volume of requests. However, 4 weeks with zero communication — not even an acknowledgment of the support ticket — is concerning. What I'd like to know: Is there a system glitch, account flag, or hidden blocker preventing my submission from entering review? Can someone confirm my app is actually in the queue and not stuck due to a technical issue? A queue position or estimated timeline would go a long way Any visibility from the App Review team or anyone who has experienced a similar situation would be greatly appreciated. Thank you.

This is a bit complicated to explain so bare with me. I am working on building an app that allows you to send real time video/camera captures from one Apple device to another. I am using a custom UDP protocol built on top of NWListener, NWBrowser, and NWConnection APIs. It works fine, but there are a few issues that seems to all be related to awdl: When transmitting via WiFi over the router (not using peer-to-peer), there are periodic interruptions when the wireless card on the device changes channels for awdl polling. This is resolved by changing the 5GHz WiFi channel on the router to channel 149 (or disabling AWDL altogether which is not really feasible). In order to work around number 1, I decided to build in an option to toggle/prefer peer-to-peer transmission in the app thinking that if everything goes over a peer-to-peer connection the jitter caused from the channel switching should go away. This also works, but with an important caveat. The default transmission is extremely choppy until you take an OS action that “elevates” the AWDL connection into “realtime” mode. I am using includePeerToPeer on the listener, browser, and connection as well as serviceClass interactiveVideo. For number 1, you can understand that asking users to change the channel on their router is not a great user experience, but the problem is the peer-to-peer connection workaround is also not great by default. For number 2, as an example of the behavior, I can send a stream from my Mac to my iPad over a peer-to-peer connection and it works but the video is very choppy until I move my cursor from my Mac to my iPad to trigger Universal Control. I captured the OS logs while doing this and can confirm that something happens to trigger “realtime” mode on the AWDL connection. After that, the streaming is totally smooth with zero latency. Some log samples: 2026-03-19 12:42:01.277968-0400 0x1ae294c Default 0x0 495 3 rapportd: (CoreUtils) [com.apple.rapport:CLinkD] Update client from UniversalControl:697 2026-03-19 12:42:01.278031-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Connect start: 'CLink-ed3b9618b4e0._companion-link._tcp.local.%13' 2026-03-19 12:42:01.278149-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Querying SRV CLink-ed3b9618b4e0._companion-link._tcp.local.%13 2026-03-19 12:42:01.279454-0400 0x1ae253a Info 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] Created AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> 2026-03-19 12:42:01.279498-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Resolving DNS f970afcc-1f1c-47af-a3f3-0236c9f9bbb0.local.%13 2026-03-19 12:42:01.279588-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> was started 2026-03-19 12:42:01.282537-0400 0x1ae294c Default 0x0 495 0 rapportd: (Network) [com.apple.network:path] nw_path_evaluator_start [5C54D967-624D-4269-B080-6C7AE63218C7 IPv6#1e905043%awdl0.49154 generic, attribution: developer] path: satisfied (Path is satisfied), interface: awdl0[802.11], dns, uses wifi 2026-03-19 12:42:01.596450-0400 0x1ae253a Debug 0x0 382 0 wifip2pd: [com.apple.awdl:driver] Received event realtimeMode 2026-03-19 12:42:01.596589-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:interface] Realtime mode updated true I noticed that on iOS 26 and iPadOS 26 a realtime mode was added specifically to the Wi-Fi Aware API which I assume does what I want: https://developer.apple.com/documentation/wifiaware/waperformancemode/realtime, but I am looking for a solution that works with the existing network API and also on previous OS versions. I have already tried a lot of things, but is there any way to programmatically trigger “realtime” mode? For additional context, the goal here is to have extremely low latency that also works for gaming. The actual latency introduced in 1 is approximately 30-50ms around once a second… adding a buffer to the stream makes the video completely smooth, but the extra delay on the receiver end is not acceptable for this use case. Any help or ideas would be appreciated. I can’t easily share a reproduce case right now, and even if I could, getting multiple devices into the exact state along with the router configuration in order to reproduce is going to be pretty difficult anyway.

Currently we are building a service based on Fairplay SDK version 26.0. Currently our solution is using version 4.5.4. When we run the below request to get version we get proper response curl http://xx.xx.xx.xx:8080/fps/v Response - V26.0 Our client applications call below two APIs https://GW_HOST:8080/fairplay_cert https://GW_HOST:8080/fairplay_license Within the cert API call, we are returning the fairplay public certificate. Currently we are trying to use the test certificate provided along with Fairplay SDK (test_fps_certificate_v26.bin) Then within the fairplay_license API call, we are trying to reach fairplay service based on Fairplay SDK v26 We are seeing some issues with below request(attaching the request json payload) curl -v -X POST \ -H "Content-Type: application/json" \ -d @SDKValidation.json \ http://xx.xx.xx.xx:8080/fps SDKValidation.json We are getting "Empty response from server" When we checked the apache error logs in the file "/etc/httpd/logs/error_log" we see some exception. We are sharing the traces in a file (ApacheErrorLogs.txt). ApacheErrorLogs.txt Also if we use old pblic key used with version 4.5.4, we are getting another error from service. {"fairplay-streaming-response":{"create-ckc":[{"id":1,"status":-42605}]}} Can you please help us with the reason of this failure?

Hi, I've seen a few posts about payment been declined, with no resolution noted on any. I have tried, Chrome and Safari, with the same response - Payment Declined. Checking my bank that payment request never reached them, so the issue lies with Apple's payment system, maybe their fraud prevention on payments. Im using my companys debit card to make the payment. How can i get this resolved? Thanks Lee

Providing a response and feedback to this: https://origin-devforums.apple.com/forums/thread/827311 and https://developer.apple.com/forums/thread/827043?page=1#889020022 I have a created a feedback/bug report with ID FB22823733 Feedback Report: I have created a feedback report as well like recommended with this ID: FB22823733, with more elaborate images of my implementation, also see here More clarity: Yes, this is for an iOS app(iOS 18+) but testing and debugging on Xcode(MacOS 15.7.7, M4 24GB), which traps or hangs on getting to [PhotogrammetrySample] even while using the lazy sequence and the contentsOf as specified in your docs. I also tried using the PhotogrammetrySession folder run but its still failed with : CoreOC.PhotogrammetrySession.Error 6 and I understand to mean alignment failed. What can be done or do you guys expose any functions that can be used to aid, or handle these internally, can't find any internally. The ObjectMasks are actually segmentation masks from an ML algorithm . To replicate try calling PhotogrammetrySession(input: [PhotogrammetrySample]) with contentsOf as captured on your documentation, even with like 30 image set or is there something I'm missing.

What is the amount of time that the app review board takes to respond to an appeal? My app was rejected on May 4th and I submitted my appeal to the review board on May 12th. I am just curious if there is a general timeframe, if I need to reach out to support or what the best course of action should be?

Hi everyone! Today I finally submitted my first iOS app for App Store review after previously publishing the Android version on Google Play. App ID: 6771439707 The app was developed with Flutter and the process was a very interesting learning experience, especially around: App Privacy configuration screenshots and metadata archive/distribution process App Store Connect setup adapting branding/assets to platform guidelines Coming from Android publishing, I have to admit the Apple review pipeline feels much stricter and more detail-oriented 😄 but also very polished once everything is correctly configured. I just wanted to thank the community because many forum posts helped me solve issues during the submission process. Now waiting for review results 🤞 Greetings from Argentina!

Is it normal for an app to wait for review for more than a 7 days? Never happened to me before, but this is getting too frustrating now.