Overview

I'm posting here after 8 months of back-and-forth with Developer Support (case 102685152651) because I've exhausted that channel and need to know if others have experienced this or if any Apple engineers can advise. The issue: When a user types "Dabah" — the exact name of my app — the App Store autocorrects/redirects to "Sabah." My app does not appear in those results. It only appears when the user searches "Dabah recipes." This means users who know the app by name cannot find it unless they add a secondary keyword. What makes this clearly a system-level bug, not a ranking issue: The same behavior occurs inside Apple's own Developer Marketing Tools portal. Searching "Dabah" returns only Sabah-related apps. Searching "Dabah recipes" finds my app immediately. This is not a user-facing algorithm issue — it's happening in an internal Apple tool. "Dabah" is a unique, uncommon word with no major competing apps. There is no legitimate reason an exact-name search should be overridden. The app has been live on the App Store since mid-2024, is properly indexed (it surfaces on keyword searches), and has "Dabah" listed as a keyword. The problem is specifically in the autocorrect/normalization layer treating "Dabah" as a misspelling of "Sabah." I've submitted screen recordings demonstrating both behaviors. Developer Support has confirmed my ticket is with the engineering team, but I've received no resolution or timeline in 8 months. Has anyone else encountered autocorrect overriding an exact app name match? Is there a known path to escalate search indexing bugs beyond the standard Developer Support channel? App: Dabah (id6745241806) Category: Food & Drink

Hello Team, We’ve confirmed Apple’s current minimum OS requirements for Xcode 26: iOS 15 – 26 iPadOS 15 – 26 tvOS 15 – 26 watchOS 8 – 26 visionOS 1 – 26 macOS 11 – 26 Are we correct in understanding that any builds targeting below these versions are no longer accepted by the App Store and may fail to launch for users on older systems? Like this https://developer.apple.com/forums/thread/821370?answerId=882822022#882822022 For Steam macOS distribution, can older macOS targets still be supported, or should we align strictly with Apple’s minimums? Thank you and best regards, Phong

We're seeing some strange behavior of the appAccountToken when passing it to a purchase in the sandbox environment. Normally we'd expect the same account token to be set on the resulting verfication, but that's not the case. Instead the token seems to be persisted on the API side and reused for some amount of time, meaning there's a mismatch and the connection between account and purchase is lost. This happens consistently even if we send new tokens on each purchase. Has there been any updates to purchase flow in the sandbox environment on Apple's side? .purchase( options: [.appAccountToken(token)] )

hello last year at the WWDC Apple announced a app extension for audio playback in CarPlay for iOS apps is there a guide to add this feature because whenever I open my custom music I can hear the music playing trough the car's speakers and I see the album art, but I have no controls on the display of the car the person I white this app for is a indie producer who wants his huge collection to be available for people to enjoy there is no subscription of login

Hi, it's very urgency! https://developer.apple.com/forums/thread/818346 After long time preparation, We finally execute this transfer operation today. Works fine at preliminary stage, lots of users had been transferred successfully. However, about 25% users transferred failed at the end, 'invalid_request' response from https://appleid.apple.com/auth/usermigrationinfo. No matter how many times we retry, it does work. Please help! 700,000 users are waiting us!

I'm seeing this repository issue on my ASC Xcode Cloud page, and when I click "Reconnect" it shows me a lovely huge green checkmark with "GitHub has been successfully connected." but the error remains, and I cannot kick off new builds.

Code: func pushRegistry(_ registry: PKPushRegistry, didReceiveIncomingPushWith payload: PKPushPayload, for type: PKPushType, completion: @escaping () -> Void) { print("📶 收到 VoIP 推送: (payload.dictionaryPayload)") JPUSHService.handleVoipNotification(payload.dictionaryPayload) // 解析来电信息 guard let voipInfo = payload.dictionaryPayload["_j_voip"] as? [String: Any] else { completion() return } let caller = voipInfo["relationship"] as? String ?? "未知来电" apiUserId = "\(voipInfo["apiUserId"] ?? "")" let callUUID = UUID() // 关键：直接调用 reportIncomingCall // 虽然 Task 是异步的，但我们已经用 @preconcurrency 标记了类 // 并且 PushKit 的 completion 会在之后立即调用 self.reportIncomingCall(uuid: callUUID, callerName: caller) // 立即调用 PushKit completion completion() } private func reportIncomingCall(uuid: UUID, callerName: String) { print("========来电了============="); currentCallUUID = uuid isCallNotAnswered = true let handle = Handle( type: .generic, value: callerName, displayName: callerName ) var update = Conversation.Update( localMember: handle, members: [handle], activeRemoteMembers: [handle] ) // 👇 关键：设置通话能力为支持视频和播放铃声 update.capabilities = [.video, .playingTones] // ✅ 修复数据竞争警告 Task { do { try await conversationManager.reportNewIncomingConversation(uuid: uuid, update: update) print("✅ LiveCommunicationKit 来电上报成功") } catch { print("❌ 来电上报失败: \(error.localizedDescription)") } } } When the app is in the background and VoIP messages arrive, the program crashes. The error message is:*** Assertion failure in -[PKPushRegistry _terminateAppIfThereAreUnhandledVoIPPushes], PKPushRegistry.m:349 *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Killing app because it never posted an incoming call to the system after receiving a PushKit VoIP push.' *** First throw call stack: (0x18df82044 0x18b419abc 0x18d27d6d0 0x21cff5494 0x107486064 0x10747d19c 0x21cff46fc 0x10746c584 0x107486064 0x1074a6f98 0x10747c548 0x10747c484 0x18ded4b74 0x18de782c4 0x18de79a0c 0x1dad01454 0x1908991a4 0x190864a28 0x10435fa1c 0x1b4965f08) libc++abi: terminating due to uncaught exception of type NSException Debug session ended with code 9: Terminated due to signal 9

I'm unable to enrol into the Apple Developer Program, I tried it one, and then the button was disabled after. I'm also unable to access it via the website, please any help.

I have a device which is using linux gadget audio to receive audio input via USB, exposing 24 capture channels. This device works well with Mac, Windows, and Android phones. However, when sending audio from an iPhone (both USB-C iPhones and lightning iPhones using an official Apple lightning -> usb adaptor) I am seeing strange behaviour. Audio which is sent from the iPhone to any one of inputs 12, 19, 20, 21, or 22 appears in all of those channels, rather than only the channel to which audio is routed. I have confirmed on my linux device that these channels are not being erroneously populated by the software running on that device; the issue is visible in audio recorded directly from the gadget using arecord, meaning it is present in the audio being sent from the iPhone. I have confirmed that the gadget channel mask is correct for 24 channel audio (0xFFFFFF). As said above, audio routed to this device from any non-iPhone device (Mac, Windows, Android) works fine. The only sensible conclusion seems to be that the iPhone is populating the additional channels erroneously due to some bug in CoreAudio's handling of gadget audio devices. I would appreciate any insight on this from Apple developers, or from anyone else who has come across this issue and found a workaround.

I'm developing an iOS app that uses Apple's DockKit framework to control gimbals. I've tested with the Insta360 Flow 2 Pro and the DJI Osmo Mobile 8. The Flow 2 Pro supports all DockKit motor control APIs — setAngularVelocity, setOrientation, setLimits — which lets my app do manual pan/tilt control via a virtual joystick. The Osmo Mobile 8 (model DS308, firmware 1.0.0) connects fine via DockKit and reports as docked, but every motor control API fails with "The device doesn't support the requested operation": setAngularVelocity — fails setOrientation(relative: true) — fails setLimits — fails The only thing that works is Apple's system tracking (setSystemTrackingEnabled(true)) for automatic face/body following. This means there's no way for third-party apps to do manual gimbal control (pan/tilt via joystick) on the Osmo 8 through DockKit — only automatic tracking works. Questions: Is anyone else seeing the same limitation with the Osmo 8 and DockKit? Has DJI confirmed whether manual motor control via DockKit is intentionally unsupported, or is this a firmware issue that might be addressed in an update? Does the DJI Mimo app use DockKit for its tracking, or does it use a proprietary Bluetooth protocol? Running iOS 26.4 on iPhone 15 Pro. Happy to share more technical details if helpful.

Whenever I try and talk to chatgpt codex in Xcode, I get the request could not be completed error with this tag: JSON-RPC global stream failed: The operation couldn’t be completed. (IDEIntelligenceAgents.JSONRPCElement.Error error 1.) Chatgpt chat still works inside of xcode, however codex does not work. I have not hit my limit for codex. This issue happened after the xcode update. (I belive 26.4.1)

I’m trying to find out whether anyone has seen this kind of App Store Connect issue remain unresolved for this long. This is for a first auto-renewable subscription. Timeline: Original support case opened: Feb 27, 2026 Support initially repeated the normal guidance that the first subscription must be submitted with the app version I explained that the issue was not the process itself, but a stuck review state On Mar 25, 2026, I was told the case had been escalated to the appropriate internal team Since then, I have sent follow-up emails asking for status / owner / ETA As of Apr 12, 2026 (KST), there has still been no meaningful update Current state in App Store Connect: App version 1.0.10 is still “Prepare for Submission” Previous 1.0.10 submissions show as “Deleted” There is no active app review submission for 1.0.10 The subscription previously showed “Waiting for Review” Now the subscription itself shows “In Review” But its localization still shows “Waiting for Review” So the state looks inconsistent: no active app review submission app version still draft subscription partially moved into review anyway At this point I’m not asking about the normal first-subscription submission flow. I already understand that. What I’m trying to understand is: Has anyone seen a case like this stay stuck for 6+ weeks? Has anyone had Apple say it was escalated internally and then go silent for weeks? Did Apple eventually fix it manually? Is this something that can remain stuck indefinitely unless the internal team intervenes? Any comparable experience would be helpful. Apple Support keeps saying that the internal team will follow up with me directly if they need anything. Is there anything I can do, or is all I can do just wait? Here are the relevant screenshots. App Review history: no active review for version 1.0.10, previous submissions are deleted Subscription page: the subscription itself is now “In Review” Localization on the same subscription page still shows “Waiting for Review” App version page: 1.0.10 is still “Prepare for Submission” There’s no subscription check.

Safari continues to display a "Fraudulent Website Warning" for openvan.camp despite the domain being clean across all major security databases for over a week. Chrome, Firefox, and all other browsers open the site without any warnings. Domain: openvan.camp Warning appeared: March 18, 2026 Warning type: Fraudulent Website Warning (red screen) Current security database status: Google Safe Browsing: ✅ Clean (transparencyreport.google.com) Google Search Console: ✅ No security issues Spamhaus DBL: ✅ Removed from blocklist Fortinet FortiGuard: ✅ Category "Travel" VirusTotal: ✅ 0/65 vendors URLVoid: ✅ 0/35 engines Steps taken: Removed the third-party ad network (Adsterra) that caused the original flag — March 18, 2026 Migrated hosting to Scaleway (AS12876, France), IP: 151.115.84.228 Configured SPF, DKIM, DMARC records Created functional abuse@ and postmaster@ role accounts Submitted review via websitereview.apple.com — no response after 5 days What we believe is happening: Apple's Safe Browsing database appears to have an independent entry for this domain that has not been updated despite all underlying security databases clearing the flag. Safari's warning persists even after deleting ~/Library/Safari/SafeBrowsing/ cache and re-downloading the database — which confirms this is not a local cache issue. Steps to reproduce: Open Safari on macOS or iOS Navigate to https://openvan.camp/ Safari displays "Fraudulent Website Warning" Open the same URL in Chrome — no warning Expected behavior: No warning should be shown. The domain is legitimate, clean, and verified. Has anyone experienced a similar issue? Is there any additional channel to escalate beyond websitereview.apple.com?

Hi devs and Apple support team, I’m waiting for updates on two Apple Developer Support cases: 102870790200 102870755282 Both are related to changing my Apple Developer / App Store Connect region and entity information from UAE to Kazakhstan. The requests were submitted last Thursday (5 days ago), and I still haven’t received any update. This is currently blocking my app release. Has anyone dealt with a similar issue, and is this waiting time normal for this type of request? Thank you very much.

Is system_profiler the recommended approach for retrieving installed application data on macOS? If not, what is the preferred and reliable alternative to fetch a consistent and complete list of installed applications?

I'm building an app with a leaderboard based on users' step counts, so I need the data to sync in real time at minimum. The problem is that when the app is terminated, steps don't seem to be counted at all, so if a user hasn't opened the app in 5 days, the leaderboard ends up completely out of sync. Is it even possible to retrieve this data when the app has been terminated and hasn't been opened? I'm currently using Background Fetch, which works when the app is suspended, slowly, but it does work. However, it does not sync when the app is fully terminated.

What could be the possible reasons for my device getting a Face id hardware failure after updating the phone to 26.4.1? I am suspect there could be some failure connections between TrueDepth sensors and front camera. Can anyone try to help me here

Hey In my Business -> Compliance, Section. I found this: Directive on Administrative Cooperation - 7th Amendment " Personal services are time- or task-based work done by people (independently or for an entity) at a user's request, and enabled by a platform. These could be services delivered online or in-person by tradespeople, tutors, transportation, delivery, and other professionals. " I don't know what to answer, Yes or no. Questions: So AiChats are/is telling me that this might be only to ask if my APP(s) are like Uber and similar, letting users provide services in exhange of money? If yes, responding to this compliance form, what would it provoke? Would I have to somehow force the app and users to be able to register as companies instead of normal users, all because they are offering services and perhaps gettings money value from it? For now I am not making such apps, the app I have let people give other food (for free). BUT IF ONE DAY i introduced the money service side of it, and I have to respond to this compliance form, I would be obligated to do what? Knowing that my account is a personal account, BUT I have a small solo company in my name so I consider my personal dev account as usable. I wonder if any of this is connected and would like to know prior and learn more. Everything to know. Thanks

Hi, ı was stuck at the very beginning even before i pay for the programme, when i click to ‘enroll today’ it says ‘your application under review’ but i even did not apply and did not pay yet! It seems there is a techical problem but i am also not able to reach the support team at the programme. ı’ve been mailing and trying to call somewhere to get help. It should not be such to solve a very simple problem l!

Hello, I have a question regarding Apple's policy on third-party SDK signatures. I have reviewed the official documentation here: https://developer.apple.com/support/third-party-SDK-requirements/ Our app is developed in the following environment: Minimum Target: iOS 15 Xcode: 26.2 Engine: Unreal Engine 4.27.2 We are integrating the Firebase SDK into our project. However, we are experiencing app crashes caused by an issue within the GoogleAdsOnDeviceConversion.xcframework included in the Firebase SDK (related to a memory optimization issue in UE4). According to an official response from the Firebase team, this crash can be resolved by wrapping the Firebase SDK in a dynamic XCFramework. We have confirmed that this solution does indeed fix the crash. The problem is that wrapping the Firebase SDK in a custom dynamic XCFramework removes all of the original Firebase SDK signatures. The documentation on third-party SDK signatures, which I referenced earlier, states that a signature is required for the Firebase SDK, and this requirement also applies when repackaging it. This leads me to the following questions: Question 1: When we wrap and repackage the Firebase SDK, is it mandatory for the resulting XCFramework to still include the original Google LLC signature? Question 2: To resolve the crash, we intend to use the Firebase SDK by wrapping it in our own dynamic XCFramework (e.g., FirebaseWrapper.xcframework). When we do this, the resulting XCFramework loses the Google LLC signature, and consequently, the final built IPA's signature list does not contain any Firebase-related signatures. Will this be a reason for rejection during App Store review? Question 3: If we wrap the Firebase SDK in a dynamic XCFramework and then sign it with our own developer certificate, would this be a reason for rejection during App Store review?