Overview

I had a company in the past and created a developer account for an organization. Can I switch it back to individual? Or should I create a new one and enroll again?

Dear Review Team and fellow developers Our app has not been reviewed for more than 7 days despite requesting an expedite Is this normal? Has this happened to us too? I would like to ask the review team to help us with this. Best regards

I am currently on Apple's Dev Beta V4 for iOS 27. The first version I installed was the Dev Beta V2, I am desperate to try out the new Siri AI Beta, but it's just not installing for me. I have the ability to "turn siri off" then "on again" and find I get the 2024 Apple Intelligence version fine. But if I choose to try out the new AI Beta, I'm left with "Adding support for Siri is in progress. Siri will be unavailable until the update is complete." It's been in that state for over 48 hours in Beta 4 and I'm left with the OLD OLD Siri globe from pre-Apple intelligence. Am I being too keen and just not leaving it long enough? Or is there a genuine issue at Apple's end, in regard to getting the new Siri to actually fully install?

Hello, my app (ID: 6762866217) has been "In Review" since 11th July! I opened a ticket with Developer Support (102949889377) and was told on 23rd July that no action is needed. This is a normal small update with bugfixes, so I didn't expect the review to be difficult. I understand that there must be considerable workload, but I have never seen a delay like this and don't see anybody else reporting delays like this. Please advise. Thanks.

Is anybody else having a probelm pairing an Apple Pencil. I insert it into my new 2gen iPad Pro 12.9 and it briefly shows the dialog to Pair and then shows it connected, but then disconnects, and then I get an Error that the Pencil took to long to pair. Then it doesn't work.Am I alone in having this issue.Thanks,Nick

Deleted items can not be recovered. With thechanges in menu options, recover option for recently Deleted items is no longer available, or not discoverable. If anyone found it let me know.

Hello everyone, I'm wondering if anyone else is experiencing a similar issue with App Review. We submitted our app for review on July 24, and its status is still Waiting for Review. Since it had been several days without any progress, we opened a support ticket on July 30, but we haven't received a response yet. Has anyone else experienced unusually long review times recently? If so, how long did it take before your app moved into review or you received a response from Apple Support? Thank you in advance for sharing your experience.

We build apps at Appther, and our sleep and anxiety app DeepRest had a stubborn onboarding problem. Users installed, opened it once, and a big chunk never reached the core experience. We rewrote the flow three times before it clicked. Sharing what actually moved the needle, in case it saves someone else the loops. What did not work first: We front-loaded everything. Account creation, notification permission, and a long value-pitch carousel all before the user touched anything real. Every gate was a place to quit, and people quit. What finally worked: We let people reach value before asking for anything. No sign-in wall on launch. They could try a core session first, then create an account only when they wanted to save progress. Drop-off fell sharply at that one change alone. We primed permissions instead of demanding them. Before the system notification prompt, we showed a plain screen explaining why reminders help sleep consistency. The soft ask before the hard ask lifted our opt-in rate a lot. We cut steps and measured each screen separately. Instead of a funnel-wide number, we tracked drop-off per screen. That exposed exactly which two screens were bleeding users, which we would never have seen from the overall rate. We deferred everything non-essential. Profile setup, preferences, and personalisation moved to after first value, not before it. The lesson for us was simple. Onboarding is not where you explain your app. It is where you get the user to one real win as fast as possible, then earn the right to ask for more. Happy to go deeper on the SwiftUI side of any of this if useful. appther.com/contact-us

Submission date (Tuesday, 6:19 PM,) Apple ID: 6774936652 This has now been in waiting for Review for 4 days with no movement and no reply to my email concerning this. Its not the fist upload, its been updated every few days and hate review always goes through quickly, and this time its ground to a halt. Could someone from the App Review team confirm the submission is correctly queued?

I have a SwiftUI + SwiftData app where scrolling became very slow, and I've traced it to something about @Query I didn't expect. The app was running save for each lazy list item appearing in viewport (a separate bug, but it did highlight the problem), which made the whole list re-render on each save. After tracing why this happens I have discovered that it is because another model watched in the list parent is invalidated after every save, and the problem was that this another model has @Query in a separate view (sidebar), removing that @Query fixed the problem. Here is a minimal reproduction of this https://github.com/aytigra/QueryRefaultRepro I wonder if it is a bug or an expected behavior?

I submitted a program to Apple for review for the first time, and it passed without any issues. However, I opened a case on July 17th for unlisted distribution (for company personnel use), and today is the 14th day, and it's still pending. I'm emailing them, and they keep brushing me off with responses like, "We're very busy these days, sorry, we've forwarded it to senior, we've forwarded it to T3." Finally, they replied that they've forwarded it and they can't intervene. Those who responded to the case initially contacted me about unrelated issues, then I emailed again, and they're just stalling with the above responses. We have apps that pass Google Play in 2 days, but when it comes to Apple, it's been 14 days without a response, and it's becoming frustrating. Is there nowhere else to turn? Their last response was, "We've forwarded the issue to T3, there's nothing we can do, they will contact you." I've worked with different companies for different software before, and I've never seen such a poor support approach. Looking at the forum, most people are complaining about this situation. This is the first time I've been so disillusioned with Apple. I don't think they'll even look at this, but the app's Apple ID is: 6791923313

I'm wondering if there is something wrong with my submission. It looks normal. For the same app, prior reviews took two or three days.

Submitted my app (universal iOS app with two auto-renewable subscriptions attached, first submission) for review on July 24 at 10:50 PM. It's now been 8 days and the version has never left "Ready for Review" in App Store Connect. No reviewer assigned, no message, nothing new in the History log since the submission itself. I opened a support case with Apple Developer Support (App Review Status topic) on July 29. Got the automated acknowledgment, no human reply since. Seeing several other threads posted here in just the last day describing the exact same thing (stuck in Ready for Review / Waiting for Review, first-time submissions, some with subscriptions attached too). Wondering if this is a wider backlog right now rather than something specific to any one submission. Has anyone actually gotten a reviewer assigned after being stuck like this, or found anything that helped? Thanks.

Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.

Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.

I've been using the iOS 27 beta and noticed in Messages app that the link presentation is now customisable. Upon tapping on the link it opens (what I assume is) an edit menu interaction, which allows customising which metadata is shown. I've seen some links offer more customisation than others, presumably based on available metadata. There's also an option in the menu to convert to a text link, and when highlighting a link in text there's an option to "show link preview" which converts it to an LPLinkView. I've been wondering for a while now if it was possible to add a similar feature to my own app, allowing the user more control over the link previews. How can I achieve similar? Especially "Customise Link" sheet seen in the middle two screenshots?

We have a published, approved App Clip that works correctly via QR code and the Safari Smart App Banner, but URL-based invocation does not trigger the App Clip card in any context. Most notably, Apple's own default App Clip URL does not work either: https://appclip.apple.com/id?p=hazel-torus.Clip **Tapping this link in Messages or Notes does nothing. ** Long-pressing it shows a generic website link preview rather than the App Clip card, even though appclip.apple.com is Apple's domain and requires no configuration on our end. Setup details: App Clip bundle ID: hazel-torus.Clip Team ID: 2UNR2APH47 App Clip experience URL: https://passportreader.app/open AASA includes a correctly formatted appclips key with 2UNR2APH47.hazel-torus.Clip (confirmed via https://app-site-association.cdn-apple.com/a/v1/passportreader.app that AASA is correctly cached) Associated Domains entitlements (appclips:passportreader.app) are present on the App Clip target App and App Clip experience are both Approved / Ready for Sale Tested on two physical devices, neither with the full app installed Since QR and Safari banner invocation work, the App Clip itself and its entitlements appear correctly configured. The fact that even Apple's own appclip.apple.com URL fails, and is treated as an arbitrary website link, suggests this may be a backend indexing issue specific to this App Clip rather than a client-side configuration problem. Has anyone else encountered this, or know what could cause appclip.apple.com to not be recognized as an App Clip URL?

I'm looking for advice because I've been facing the same issue with every app submission on my Apple Developer account. Every app I submit remains in "Waiting for Review" for more than one month. The status never changes to "In Review", regardless of the app. Here's what I've already done: Contacted Apple Developer Support. Submitted an Expedited Review request. Waited well beyond the normal review timeframe. Verified that my apps are complete, functional, and comply with the App Store Review Guidelines. The problem is not limited to a single app. It affects every new submission and every app update I send for review. At this point, I'm wondering if there could be an issue with my developer account that is preventing my submissions from entering the review process. Has anyone experienced a similar situation? If so, how was it resolved? If an Apple engineer or App Review team member sees this post, I would be very grateful if someone could check whether there is an issue with my developer account or advise me on what I should do next. Thank you very much for your time and any assistance.

I have inserted a Static cells table with configuration items and a normal dynamic table for displaying results in a UITableViewController in a StoryBoard. I get no error, but still just the header is shown, none of the navigation bar or any hint of the two tables, as you may see in the pictures:

The set bitrate is not respected when kVTCompressionPropertyKey_AverageBitRate is used. constant and variable bitrates seems to work, only average that is broken. All three modes works in iOS 26.