Overview

Bonjour, Je viens ici afin d'exposer mon problème en espérant trouver une solution. En Août 2025 j'ai publié une demande afin de pouvoir développer une application Carplay de type navigation. Ma demande n'a jamais été traitée, j'ai soumis une autre demande en février, puis en avril. Toujours sans réponse. Depuis environ 3 semaines, j'appelle Apple toutes les semaines afin de demander à ce que ma demande soit traitée. J'ai bien évidemment une réponse m'indiquant que la demande était remontée, mais sans retour par la suite. Je commence à sérieusement perdre patience, et ne trouve aucune solution. Quelles seraient vos propositions ? Merci par avance pour vos retours

what can i do?

Hi everyone, I’ve been stuck on an issue with iOS Universal Links for about a week and could really use some help. The problem When tapping a Universal Link on iOS, my Flutter app opens correctly (desired behavior) — but immediately afterward, Safari opens the same link in the browser. So both the app and the browser open. This only happens on iOS. On Android everything works as expected. What works If the link is simply the domain, like: https://mydomain.com …then the app opens without triggering the browser afterward. This is the correct behavior. What doesn’t work If the link includes a path or parameters, like: https://mydomain.com/path https://mydomain.com/path?param=value …then the app opens, and then the browser opens immediately after. What I’ve tried Verified my AASA file using Branch’s validator: https://branch.io/resources/aasa-validator/ → The AASA file is valid. Universal Links do open the correct screen inside the app — the issue is the unwanted second step (Safari opening). Behavior is consistent across different iOS devices. Extra details Using Flutter. Universal Links set up with the standard configuration (associatedDomains, AASA hosted at /.well-known/apple-app-site-association, etc.). Question Has anyone encountered this issue where Universal Links with paths/params open the app and then open Safari? What could cause iOS to trigger the browser fallback even when the AASA file is valid and the app handles the link correctly? Any insights, debugging tips, or known edge cases would be incredibly appreciated!

We have changed app icon a while ago, it displayed correctly on distribution page and on other pages - with an exception of analytics - https://appstoreconnect.apple.com/analytics No matter what time range is selected it still displays old icon. Can I make something with it? It's been more then a year and it's definitely not a cache issue.

Hello, Shortcuts and App Intents don't work on simulators running iOS 26 or iOS 27. It's working fine on simulators running iOS 18. It makes testing and adopting new technologies difficult. Please check this feedback which contains a video showcasing the issue with a sample code provided by Apple: FB23342158 Regards, Axel

Bug: When SpatialTrackingSession and ARKitSession + WorldTrackingProvider are running concurrently, any WorldAnchor added via WorldTrackingProvider.addAnchor() triggers .added followed immediately by .removed—without any user call to removeAnchor(). The anchor never persists in allAnchors. import SwiftUI import RealityKit import ARKit struct ImmersiveView: View { @State private var worldTracking: WorldTrackingProvider? @State private var arSession: ARKitSession? @State private var processWorldTrackingUpdatesTask: Task<Void, Never>? var body: some View { RealityView { content in let configuration = SpatialTrackingSession.Configuration(tracking: [.world]) if let unavailableCapabilities = await SpatialTrackingSession().run(configuration) { if unavailableCapabilities.anchor.contains(.world) { fatalError("World tracking is not available on this device.") } } let worldTracking = WorldTrackingProvider() let arSession = ARKitSession() self.arSession = arSession try! await arSession.run([worldTracking]) self.worldTracking = worldTracking processWorldTrackingUpdatesTask = Task { @MainActor [weak worldTracking] in guard let worldTracking else { return } for await update in worldTracking.anchorUpdates { let worldAnchor = update.anchor switch update.event { case .added: print("Anchor added: \(worldAnchor.id)") case .updated: print("Anchor updated: \(worldAnchor.id)") case .removed: fatalError("Anchor removed unexpectedly — this should not happen in this demo scenario.") } } } } .task { try? await Task.sleep(for: .seconds(3)) guard let worldTracking else { return } do { try await worldTracking.addAnchor(.init(originFromAnchorTransform: Transform.identity.matrix)) } catch { print("Error adding anchor: \(error)") } } } } Expected: Anchors persist until explicitly removed or out of range. Actual: SpatialTrackingSession interferes with WorldTrackingProvider's anchor lifecycle, causing immediate removal. This was originally reported in 2025 (https://developer.apple.com/forums/thread/773351) , but remains unfixed in visionOS 27.0 beta. I've re-filed as FB23420195.

Hello Apple App Review Team, I hope you are doing well. I am writing again to respectfully request a priority review for our app. Our submissions have been waiting in review for more than 3 weeks, without receiving a final review decision. During this time, we have continued to submit updates with important bug fixes and improvements, but we have been unable to release them to our users due to the extended review delay. In addition, we have made more than five attempts to contact Apple Support regarding this issue, but unfortunately we have not received any response to our tickets. The requests appear to remain unanswered, with no follow-up or resolution provided so far. This situation is now significantly affecting our users, as critical issues that have already been fixed are still present in the live version. Each additional day of delay continues to impact the user experience. We fully understand and respect the App Review process and workload. However, given that the waiting period has now exceeded three weeks and there has been no response from support despite multiple attempts, we kindly ask if our latest version of our app could be prioritized for review. For reference, our Apple Developer account / Apple ID is: 6475698369 We would greatly appreciate any update or assistance your team can provide regarding the status of our submission.

FB: https://feedbackassistant.apple.com/feedback/22556883 We're seeing a small number of production users where both Transaction.currentEntitlements and Transaction.all return zero transactions for a valid, active, non-refunded non-consumable IAP. This makes it impossible to restore the purchase via any StoreKit 2 API. Environment: Xcode 26.4 (Build 17E192) iOS 26.4.1 Direct call to SK2 Transactions.all & Flutter in_app_purchase package v3.2.3 (uses SK2 on iOS 15+) Non-consumable IAP (one-time purchase) What we observe: AppStore.sync() triggers but the purchase stream returns 0 transactions Transaction.all returns empty Transaction.currentEntitlements also returns empty User is confirmed on the correct Apple ID Issue reproduces on both iPhone and Mac for the same Apple ID Issue appears to have started recently for users who previously had no problems Debug log from affected production user: [2026-04-20T08:50:10.744115Z] init: iapAvailable=true [2026-04-20T08:50:10.744566Z] init: isPremium=false [2026-04-20T08:50:10.744567Z] init: triggering silent restorePurchases [2026-04-20T08:50:45.974566Z] restore: started [2026-04-20T08:50:45.986848Z] restore: sk2Transactions count=0 [2026-04-20T08:50:45.993004Z] restore: sk2Direct isVerified=false active=null [2026-04-20T08:50:45.993011Z] restore: sk2Direct inconclusive — falling back to standard restore [2026-04-20T08:51:16.000851Z] restore: timed out after 30s — fallback isPremium=false [2026-04-20T08:51:16.000910Z] restore: completed — succeeded=false foundPurchase=false Unable to reproduce in sandbox — Transaction.all works correctly there. Appears specific to production for a small subset of users. Has anyone else seen this?

Hello, I enrolled in the Apple Developer Program on June 14, 2026. The annual fee was charged successfully and I received the receipt from Apple. I also completed the identity verification (with my driver's license). Despite this, my account has been showing "Pending" status for more than two weeks now. As a result, I have no access to App Store Connect — it shows the message "Your Apple Account is not set up for iTunes Connect," so I cannot create my app or upload a build to TestFlight. My app is finished and ready; I am only waiting for the enrollment to be completed. I have already submitted a support request by email (the form mentioned a 2 business day response time), but I wanted to open a thread here as well, since I can see from other recent posts that I'm not the only one affected. Apple Developer Support — could you please look into this and let me know why the enrollment is not being completed? I would appreciate any help getting my account activated. Thank you.

Hello, I am looking for advice regarding an unusually long App Review delay. Our app, Bien App (ID: 6769135685), has remained in "Waiting for Review" status since June 13, 2026 without any review activity or communication from App Review. Some additional context: The app is a financial services application. We have already submitted updated builds. We have opened support cases with Apple. The app has not entered "In Review" at any point. There have been no requests for additional information. What makes this situation particularly confusing is that our related application, Bien Plus, was submitted under the same developer account during this period and has already completed review and been approved. Because Bien Plus has already been reviewed and approved, we know that our developer account is in good standing and that our financial services business model has already been reviewed by App Review. At this point, Bien App has been sitting in "Waiting for Review" for several weeks. Has anyone experienced a similar situation where an app remained in "Waiting for Review" for an extended period while other apps under the same account continued through review normally? If so: Did Apple eventually review the app? Did you need to escalate through App Review Support? Did withdrawing and resubmitting help? Was there ultimately a queue issue or another explanation? Any advice or similar experiences would be greatly appreciated. Thank you.

When using AccessorySetupKit to remove accessories, a pop-up window appears when calling removeAccessory. However, the text in the pop-up window does not change according to my iPhone's language settings and remains only in English. Has anyone encountered this issue? Does Apple have any plans to address this compatibility issue?

I find these sample projects quite valuable: https://developer.apple.com/documentation/widgetkit/emoji-rangers-supporting-live-activities-interactivity-and-animations https://developer.apple.com/documentation/coredata/sharing-core-data-objects-between-icloud-users . Both use Swift 5, and it is not trivial to adopt Swift 6 with them. Any plans to update them? What is best approach for adopting Swift 6 on such sample code?

Hello, everyone, I've started a thread and got a recommendation from DTS Engineer to move the conversation here. The sample code for https://developer.apple.com/documentation/coredata/sharing-core-data-objects-between-icloud-users is with Swift 5. I have a Swift 6 project and I'm running into issue porting the sample code. I've found that NSManagedObjectContext is sendable (https://fatbobman.com/en/posts/sendable-nsmanagedobjectcontext/). From it I can get the persistence controller, and from it I get the stores and this solves the Swift 6 migration path and looks good. i.e. not rely on the private and shared references to the persistence stores, I'll be getting them from the context. I've also notices that once I start to change the PersistenceController from lazy vars for lazy var previewContainer: NSPersistentCloudKitContainer and lazy var persistentContainer: NSPersistentCloudKitContainer to struct PersistenceController { static let shared = PersistenceController() @MainActor static let preview: PersistenceController = { let result = PersistenceController(inMemory: true) which is the default pattern for new CoreData applications (Xcode 26 / Xcode 27) I start getting preview crashes similar to https://developer.apple.com/forums/thread/654126. It turns out this is because of let persistenceController = PersistenceController.shared in the App. Quite unexpected. The persistence controller looks more suitable for actor based on the CloudKit sharing requirements. I saw such question on WWDC 26, however there was not enough time for an answer - is a good pattern to have the PersistenceController as an actor or in another way. Which is that most swiftly way for Swift 6?

Hi, I have been testing Xcode 27 beta 2 on macOS 27 beta 2 on a MacBook Air M2 (base model) with 16 GB of memory. When loading previews for the first time, it could take a while, but it looks significantly longer compared to Xcode 26.x on macOS 26.x. Then when trying to launch a simple app with a few screens, the Device Hub takes forever, and then on Activity Monitor, the swap used starts to climb up, almost as high as 12 GB or more. Running an app on Device Hub is almost impossible. Is this a limit of what a MacBook Air can do? This is not my primary machine by the way.

Mac Store search results now default to IOS Apps, devastating Mac Catalyst sales. To compound this issue, there is no way for Mac Catalyst developers to remove their Mac Catalyst version so that their IOS app (for iPad) will appear. They are invisible. I've contacted Apple but no reply yet. Any thoughts?

I was hoping this was fixed in Beta 2, but I am having the same issue. I run my app: on a simulator device Device Hub opens Begins installing the app I see the icon and it starts to fill in The launch screen loads and never finishes loading. I then stop running app in Xcode. Device Hub still shows launch screen I restart device in Device Hub I then can open the app and test Anyone else experiencing this? I would really like to solve this as it makes testing changes a frustrating experience. Because I then have to close Device Hub and Xcode to simulate again.

Today, I picked up on my work on the Gaussian Splats demo from Apple I was working with last weekend, and it didn't work (I've updated everything to beta 2 this week). I tried downloading a fresh copy of the demo (in case I screwed mine up), and not only does it work, it can load Gaussian Splats data from a USDZ file. Am I mis-remembering what the demo was like last week vs. this week? This feels like major new functionality I haven't heard mentioned anywhere. Is there any documentation/guidance on how to package up Gaussian Splat data (e.g., originally from a PLY file) into a USDZ file?

ChatGPT stopped working in Xcode MacBook Air M2 2022 MacOS 26.5.1 Xcode 26.5 ExpressVPN Version 11.71.0 (90727) Internet connection is working fine. On late night June 22, ChatGPT in Xcode was working fine. Then I started getting “cannot complete” messages with “network error”. Now ChatGPT in Xcode does not work at all. My subscription to ChatGPT auto-renewed on June 23. My bank confirms that the payment went through. I logged into ChatGPT in Safari and Firefox. The account looks fine. In Xcode settings/Intelligence/ChatGPT in Xcode, the Usage Limit says Under Limit. I signed out of ChatGPT from within Xcode, and signed back in. It still is not working. I quit and restarted Xcode, then signed out of ChatGPT again, and signed back in. Still not working. Restarted my Mac, opened Xcode. It still doesn’t work. Signed out and back into ChatGPT in Xcode. ChatGPT still is dead. Disabled VPN. Quit and restarted Xcode. ChatGPT still not working. 1-800-ChatGPT was no help at all. I can use ChatGPT while logged into my account on their website. I told it “ChatGPT in Xcode has stopped working”. It came back with: “I’ll help narrow this down. I’ll check current official OpenAI guidance/status first, then give you the fastest troubleshooting path for Xcode specifically. Thought for 6s Try this order: 1 Update ChatGPT for macOS — Work with Apps/Xcode needs ChatGPT macOS 1.2025.057 or later. 2 Restart both apps: quit ChatGPT and Xcode completely, then reopen Xcode first, ChatGPT second. 3 In ChatGPT macOS, check Work with Apps is enabled and Xcode is selected/available. 4 macOS permissions: System Settings → Privacy & Security → Accessibility and Automation. Make sure ChatGPT is allowed to control/read Xcode. 5 In Xcode, open an actual source file and put focus in the editor, then try ChatGPT again. 6 Check OpenAI status; current status page shows ChatGPT service status and incidents. 7 If on corporate/VPN network, try off VPN; OpenAI notes TLS/SSL inspection can break app access. Most common fix: update ChatGPT macOS + re-grant Accessibility/Automation permissions.” I never had the app ChatGPT for MacOS. I set up an account on ChatGPT.com and enabled it in Xcode. That was working fine until the June 23. ChatGPT is not in System Settings → Privacy & Security → Accessibility. Downloaded ChatGPT for MacOS. Quit Xcode. Added ChatGPT to. System Settings → Privacy & Security → Accessibility. Started ChatGPT. Started Xcode. Signed out of ChatGPT in Xcode, and signed back in. ChatGPT in Xcode still is dead. I am at a complete loss. Can anyone help? Doug

My iOS app update version 1.1, build 12, has been stuck in “Waiting for Review” for an unusually long time. The app has not moved to “In Review” yet. At first, I found that there were some account/compliance items that needed attention. I have since resolved them and carefully checked App Store Connect. Currently, I do not see any remaining “Action Required,” “Missing Metadata,” “Missing Compliance,” or “Developer Action Needed” status. Here is what I have checked: Apple Developer Program License Agreement: accepted Paid Apps Agreement: active Banking and tax information: valid EU DSA / trader status: completed EU countries have been removed from app availability Monthly and yearly subscriptions: approved Subscription group localization: approved Privacy Policy URL and Support URL: accessible App Privacy information: completed Export compliance: no Missing Compliance or Waiting for Export Compliance status App Review Information: completed Selected build: version 1.1, build 12 Current app status: Waiting for Review I also contacted Apple Developer Support, and the response indicated that the app has been added to the App Review queue, but the review has not started yet. No further action was requested from my side. The reason I am concerned is that the current live version 1.0 has issues affecting the core user workflow. Some users may be unable to reliably start or continue experiment records, and version 1.1 includes fixes and improvements for experiment creation, record management, backup/recovery, and record viewing. Has anyone experienced a similar situation where an app update remained in “Waiting for Review” for an unusually long time even after all agreements, subscriptions, DSA, privacy, and build settings were completed? Is there anything else I should check, or is this likely an internal queue issue that needs to be escalated by App Review? Thank you.

Hi all, I'm building an iOS app extension using ExtensionKit that works exclusively with its containing host app, presenting UI via EXHostViewController. I'd like the extension to have read-only access to the host's task for process introspection purposes. I'm aware this would almost certainly require a special entitlement. I know get-task-allow and the debugger entitlement exist, but those aren't shippable to the App Store. I'm looking for something that could realistically be distributed to end users. My questions: Does an entitlement exist (or is one planned) that would grant an extension limited, read-only access to its host's task—given the extension is already tightly coupled to the host? If not, is this something Apple would consider adding? The use case is an extension that needs to inspect host process state without the ability to modify it. Is there a path to request such an entitlement through the provisioning profile process, or is this fundamentally off the table for App Store distribution? It seems like a reasonable trust boundary given the extension already lives inside the host's app bundle, but I understand the security implications. Any insight appreciated. Thanks!