Overview

Hello everyone I'm currently experiencing an error when submitting a public link for internal downloads. When I submit and review, it says: "There was an error processing your request. Please try again later." I've reported this to the support team but haven't received a response yet. I would be very grateful if the technical team on this forum could help me. Case ID: 102861441465

For some reason, Carplay 18.x works fine, however in under certain situations in our app, Carplay 26.x breaks. The expected grid layout should be : However, this is what we see in some cases when we update our templates. I have not been able to isolate the cause of this issue. Has anyone ever seen this happen on their CarPlay apps and discovered the cause? The data sets fed into the templates are identical, the difference is in some of the timing and update order...

Hello there everyone. I've got numerous support projects using old school development. Things from Objective-C to RxSwift and UIKit. I've tried the LLM/Agents and they just destroy the codebase over time, so I have given up. The final straw was trying to get it to fix a POSTCODE validation issue which was using some novel ways to provide validation in place using RxSwift. Has anyone had any luck with these LLMs on Legacy codebases? Would love to hear tips.

We have an VoiP application, our application can be configured to amplify the PCM samples before feeding it to the Player to achieve volume gain at the receiver. In order to support this, We follow as below. If User has configured this Gain Settings within application, Application applies the amplification for the samples to introduce the gain. Application will also set the AVAudioSessionCategory to AVAudioSessionCategoryPlayback Provided the User has chosen the output to Speaker. This settings was working for us but we see there is a difference in behaviour w.r.t Volume Level System Settings between OS 26.3.1 and OS 26.4 When user has chosen earpiece as Output, then we will set the AVAudioSessionCategory to AVAudioSessionCategoryPlayAndRecord. User would have set the volume level to minimum. When user will change the output to Speaker, then we will set the AVAudioSessionCategory to AVAudioSessionCategoryPlayback. The expectation is, the volume level should be of AVAudioSessionCategoryPlayback what was set earlier instead we are seeing the volume level stays as minimum which was set to AVAudioSessionCategoryPlayAndRecord Could you please explain about this inconsistency w.r.t Volume level.

Hi everyone, I’m experiencing a serious issue with my app review process on App Store (Apple ID: 6760103989). My app has been stuck in review for a very long time — I’ve contacted Apple Developer Support multiple times, had my case escalated, waited over 20 days after escalation, requested an expedited review, and already posted on the forum. I received this response from Apple (Mar ’12): “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, since then, there has been no follow-up, the app is still stuck, and there is no reviewer activity (no login detected in my app). At this point, I’m extremely frustrated and actively losing users who pre-subscribed for the iOS app on release. I don’t understand what is causing the delay, whether something is wrong with my app, or what I can do to move the process forward. Has anyone experienced something similar or found a way to resolve this? Any advice would be greatly appreciated.

Re. APP ID 6758894172 This app was submitted on February 16, and since then it has been showing as waiting for review. I have contacted the support email multiple times as well as requesting the review to be expedited, but no response and no change in app status. Could you please investigate this matter and let me know what the issue is?

My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.

After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are "already enough of these apps on the App Store." While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid "category quota" can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers, regardless of how much innovation the new app brings to the table. Ultimately, we believe this limits consumer choice. Users deserve the opportunity to discover and decide between new, modern alternatives, rather than having their options restricted by a pre-determined saturation limit. We hope Apple reconsiders how 4.3(b) is applied, ensuring that the App Store remains a place where truly innovative apps, regardless of their category, have a fair chance to be evaluated on their own merits.

Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.

Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.

Hello everyone, My app (ID: 6758741935) was submitted on Feb 15, 2026 at 3:51 PM, 2026, and has been stuck in "Waiting for Review" status for over 50 days. I contacted Developer Support and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds 50 days.. Any recent experiences with long queues? Thanks!

Now I consider myself a pretty patient person. But I have been waiting over 3 weeks for a very simple app review of a point release of my app. Which is holding up months of work which is live on android. I have tried the accelerate your review process and it led no where. It's quite disappointing that things like this happen and there seems no accountability or tracking for its resolution.

Hello everyone, My app has been stuck in "Waiting for Review" for a long time, and I would like to know whether this is normal or whether I should take any additional action. App name: ختمة يومية Submission date: March 7, 2026 at 3:34 AM Current status: Waiting for Review I have already completed the required app information, including the TestFlight/App Review details, and there are no visible missing items in App Store Connect. I would like to ask: Is this review delay normal at the moment? Has anyone experienced a similar delay recently? Is there anything else I should check in App Store Connect? Would contacting App Review again help in this case? I would appreciate any advice or shared experience. Thank you.

Hello. My developer membership is expired. I cannot renew because the renewal option/button does not appears in any device. A banner tells me: "Any apps you had on the App Store are no longer available for download and you can no longer access membership benefits. If you’d like to renew your membership to reinstate your apps and membership benefits, open the Apple Developer app on your iPhone, iPad, or Mac. Sign in to your account, tap/click Renew, and follow the prompts.If you agreed to the Paid Applications Agreement, you’ll need to agree to it again after renewal in the Agreements, Tax and Banking section of App Store Connect." However, there's no "Renew" to tap or click anywhere in the app nor in the web. Any ideas? Thanks a lot.

Hello, I have an app that is using iOS 26 Network Framework APIs. It is using QUIC, TLS 1.3 and Bonjour. For TLS I am using a PKCS#12 identity. All works well and as expected if the devices (iPhone with no cellular, iPhone with cellular, and iPad no cellular) are all on the same wifi network. If I turn off my router (ie no more wifi network) and leave on the wifi toggle on the iOS devices - only the non cellular iPhone and iPad are able to discovery and connect to each other. My iPhone with cellular is not able to. By sharing my logs with Cursor AI it was determined that the connection between the two problematic peers (iPad with no cellular and iPhone with cellular) never even makes it to the TLS step because I never see the logs where I print out the certs I compare. I tried doing "builder.requiredInterfaceType(.wifi)" but doing that blocked the two non cellular devices from working. I also tried "builder.prohibitedInterfaceTypes([.cellular])" but that also did not work. Is AWDL on it's way out? Should I focus my energy on Wi-Fi Aware? Regards, Captadoh

Hello! I have an iOS app where I am looking into support for visionOS. I have a whole bunch of gestures set up using UIGestureRecognizer and so far most of them work great in visionOS! But I do see something odd that I am not sure can be fixed on my end. I have a UITapGestureRecognizer which is set up with numberOfTouchesRequired = 2 which I am assuming translates in visionOS to when you tap your thumb and index finger on both hands. When I tap with both hands sometimes this tap gesture gets kicked off and other times it doesn't and it says it only received one touch when it should be two. Interestingly, I see this behavior in Apple Maps where tapping once with both hands should zoom out the map, which only works sometimes. Can anyone explain this or am I missing something?

Environment: Xcode 26.3 RC macOS 26.3 (25D125) (Apple Silicon / arm64) Setup: Xcode > Settings > Intelligence > Claude Agent: Signed In (account status shows "Signed In") Model: Default Steps to reproduce: Open a new chat in Xcode's Coding Assistant Select "Claude Agent" from the agent dropdown (instead of "Claude Sonnet 4.5") Send any message (e.g. "HI") Expected result: Claude Agent responds normally. Actual result: The message is sent but immediately returns the error: "Your request couldn't be completed." 🚩I have an active Claude Code subscription with remaining usage. Running claude in Terminal works perfectly, confirming the subscription and quota are valid.

EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2 Platform: iOS 17+ | Hardware: Custom MFI-certified accessory (USB-C, iAP2) | Language: Swift Problem We have a custom MFI-certified accessory communicating over USB-C using ExternalAccessory. The app calls EASession(accessory:forProtocol:) after receiving EAAccessoryDidConnect but it always returns nil. We never get past session creation. What we have verified We captured a sysdiagnose on-device and analysed the accessoryd-packets log. The full iAP2 handshake completes successfully at the OS level: USB attach succeeds MFI auth certificate is present and Apple-issued Auth challenge and response complete successfully IdentificationInformation is accepted by iOS — protocol string and Team ID are correct EAAccessoryDidConnect fires as expected iOS sends StartExternalAccessoryProtocolSession — the OS-level session is established So the hardware, MFI auth, protocol string, and Team ID are all correct. Despite this, EASession(accessory:forProtocol:) returns nil in the app. We also confirmed: Protocol string in UISupportedExternalAccessoryProtocols in Info.plist matches the accessory exactly Protocol string in code matches Info.plist App entitlements are correctly configured EAAccessoryManager.shared().registerForLocalNotifications() is called before connection Current connection code @objc private func accessoryDidConnect(_ notification: Notification) { guard let accessory = notification.userInfo?[EAAccessoryKey] as? EAAccessory else { return } DispatchQueue.main.asyncAfter(deadline: .now() + 1.0) { self.tryConnectToAccessory() } } private func tryConnectToAccessory() { DispatchQueue.main.asyncAfter(deadline: .now() + 3.0) { for accessory in EAAccessoryManager.shared().connectedAccessories { let session = EASession(accessory: accessory, forProtocol: "") // session is always nil here } } } Questions The packet log shows a ~4 second gap between EAAccessoryDidConnect firing and iOS internally completing session readiness (StartExternalAccessoryProtocolSession). Is there a reliable way to know when iOS Is it actually ready to grant an EASession, rather than using a fixed delay? Is there a delegate callback or notification that fires when the accessory protocol session is ready to be opened, rather than relying on EAAccessoryDidConnect + an arbitrary delay? Are there any known conditions on iOS 17+ under which EASession returns nil even though the iAP2 handshake completed successfully at the OS level? Is retrying EASession after a nil result a supported pattern, or does a nil result mean the session will never succeed for that connection? Any guidance appreciated.

Hi everyone Please i need someone to explain this, I wanted to ask if anyone has experienced something similar with their payments. In March, in App Store Connect → Trends → Proceeds, I can see that my total proceeds are $343. However, in Payments and Financial Reports, Apple shows that they will pay me only $258 USD. From what I understand, taxes and Apple’s commission are already deducted when calculating proceeds, so I’m confused about why there is still such a big difference between the proceeds amount and the final payment. Has anyone faced this before or knows what could explain this gap? Thanks in advance for your help!

I have a submission that has been stuck in “Waiting for Review” significantly longer than expected, while other apps submitted from the same developer account during the same period were reviewed and approved quickly (under 2 days). Current pending submission App Store Connect ID: 6760300948 Waiting for Review - Mar 9, 2026 at 4:50 PM Related history (previous record for the same app functionality) App Store Connect ID: 6759011698 Status history: Waiting for Review - Feb 11, 2026 at 1:22 AM Developer Rejected - Feb 28, 2026 at 10:18 AM Ready for Review - Feb 28, 2026 at 11:31 AM Waiting for Review - Feb 28, 2026 at 11:31 AM Developer Rejected - Mar 9, 2026 at 3:13 PM I withdrew that earlier submission out of frustration after attempting to reduce review friction (first by changing metadata/review notes, then by withdrawing it altogether). The current pending submission (ID 6760300948) uses very conservative metadata and includes demo mode to allow straightforward testing. Can the App Review team check why submission ID 6760300948 is not progressing from “Waiting for Review”, and advise what the problem is or what information is needed to move it forward? Related similar thread: https://aninterestingwebsite.com/forums/thread/782319