Overview

Original discussion pre iOS 26 Our app uses Auth0 with HTTPS callback, we've found the issue where AASA file is not ready immediately when app is initially launched, which is the exact issue from the above link. The issue seems mostly fixed on later versions on iOS 18, however, we are seeing some indications of a regression on iOS 26. Here's some measurement over the last week. | Platform | iOS 18 | iOS 26 | |---------------|----------|--------| | Adoption rate | 55% | 45% | | Issue seen | 1 | 5 | | Recover? | Yes | No | This only 1 iOS 18 instance was able to recover after 1 second after the first try, however, all iOS 26 instances were not able to recover in couple tens of seconds and less than 1 minute, the user eventually gave up. Is there a way to force app to update AASA file? Are there some iOS setting (like using a VPN) that could potentially downgrade the AASA fetch? Related Auth0 discussion: https://community.auth0.com/t/ios-application-not- recognizing-auth0-associated-domain/134847/27

When taking a photo with UIImagePickerController, the text in "Use Photo" shifts. What could be the reason for this?

Background We are investigating Safari’s Prevent Cross‑Site Tracking feature (part of Intelligent Tracking Prevention / Link Tracking Protection) on iOS and macOS (latest versions). We fully understand and respect Safari’s privacy objectives and are not requesting any whitelisting or relaxation of protections. Our goal is to understand how Safari determines when and where query parameter stripping is applied, so we can design a compliant and predictable implementation. Based on public WebKit and privacy documentation, it is understood that Safari’s tracking prevention behavior may be influenced by: Tracker classification sources such as: DuckDuckGo Tracker Radar https://github.com/duckduckgo/tracker-radar EasyList / EasyPrivacy https://easylist.to/easylist/easyprivacy.txt WebKit privacy architecture and heuristics, including behavior described in: WebKit “Private Browsing 2.0” / Link Tracking Protection documentation https://webkit.org/blog/15697/private-browsing-2-0/ Request for Guidance To help us align fully with Safari’s privacy model, we respectfully request guidance on: How Safari determines, at a domain or subdomain level, when to apply query parameter stripping under Prevent Cross‑Site Tracking. Whether evaluation may be influenced by: Tracker classification sources (e.g., domain reputation or known tracking endpoints) Runtime network behavior (such as cross‑site analytics requests) Subdomain‑specific context or historical behavior Whether Prevent Cross‑Site Tracking is evaluated: Per navigation event Per domain or subdomain Based on cumulative or runtime signals Whether Apple recommends specific design patterns or alternatives for handling essential, non‑tracking URL data in a way that is compatible with Safari’s privacy protections. Our objective is to design a solution that respects Safari’s intent and avoids reliance on fragile or unpredictable URL‑based behavior.

Hello, For the past few days, whenever I tried to release a new app version on App Store Connect, I kept getting an "Apple Developer Program License Agreement has been updated" loop — 403 Notarization Error, which prevented me from publishing a new release. I noticed today that the issue has been resolved, but now I'm unable to upload the archive for the new app version.

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! I have app (macos and iPadOS platforms) with empbedded DEXT. The DEXT executable runs fine on both platforms (ver 26.2). Trying to execute from iPad App code: let sysExtWs = OSSystemExtensionsWorkspace.shared let sysExts = try sysExtWs.systemExtensions(forApplicationWithBundleID: appBudleId) but always getting OSSystemExtensionError.Code.missingEntitlement error. Which entitlement am I missing? 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