iOS is the operating system for iPhone.

Posts under iOS tag

200 Posts

Post

Replies

Boosts

Views

Activity

Ready for Distribution" status for 17 days - Apple Support unresponsive, need advice
Hello everyone, I'm facing an unusual issue with App Store Connect. My app has been in the "Ready for Distribution" status for over 2 weeks (17 days) now. Normally, distribution starts within a few hours after approval, but in this case nothing happens. What I already did: The app successfully passed the review (status is green / approved). Distribution is set to automatic release (I also tried manual — no difference). I submitted a ticket to Apple Developer Support via the official form few days ago. Ticket number: Case ID: 102898955253 I haven't received any response from Apple so far — not even an automated acknowledgment beyond the initial one. Checked spam/junk folders — no emails from Apple. My question to the community: Has anyone experienced such a long delay in the "Ready for Distribution" state recently? Is there any way to "nudge" the process without waiting for Apple Support? Would re-submitting a new build (incrementing the version number) help reset the state? Any advice would be greatly appreciated. Thank you.
2
0
76
2h
App Review stuck with no progress or feedback — urgent update blocked
Hello, I’m currently dealing with an App Review situation that has been stuck with no real progress and no useful feedback from Apple. App Name: Juego de Impostor: Palabras Apple ID: 6757995242 Bundle ID: com.rgioia.impostorwords Version: 1.8.0 Current Status: Ready for Review Previous Version: 1.7.0 Ready for Distribution Timeline: The app/update has been waiting for review for an unusually long time. There has been no clear movement, no rejection, no explanation, and no actionable feedback from the review team. This is especially frustrating because this is not a new experimental app or an unclear submission. The app is already prepared for release/update, and I need to push fixes and improvements for users. What I already did: Requested expedited review → approved Contacted Apple Developer Support multiple times Followed up several times Waited without receiving any meaningful update The only response I received was that the expedited review request was accepted, but after that nothing actually happened. Impact: The app/update is completely blocked I cannot release fixes or improvements There is no rejection reason to fix There is no communication from App Review I have no visibility into whether this is a review queue issue, an account issue, or a pipeline problem At this point, this does not feel like a normal App Review delay. It feels like the submission is stuck somewhere internally with no owner and no progress. Questions: Is anyone else experiencing this kind of delay recently? Is there any real way to escalate a stuck App Review case after an expedited review was already approved? Could this indicate an issue with the App Review pipeline or my account/app status? How can I get someone from Apple to actually look into the submission instead of receiving generic support replies? I understand that delays can happen, but having an app/update blocked for this long with no feedback, no rejection, and no progress is not acceptable for developers trying to maintain a live product. Any help, visibility, or escalation path would be appreciated. — Ramiro Gioia
0
0
75
11h
Crash on CardSession
We are working on an HCE application following your documentation. Almost everything is working fine except that we encounter a crash when using CardSession.init() method. We are calling CardSession.isEligible() before CardSession.init(). This crash is random and affects very few user and we did not find a way yet to reproduce this crash on our side. Our theory is CardSession.isEligible() is doing thing under the hood and make CardSession.init() cause a crash, but that just our theory. Here are some stacks : CoreNFC/NFCCardSession.swift:431: Fatal error: Previous session exists 0 libswiftCore.dylib   0x000000019ed73800 _assertionFailure(_:_:file:line:flags:) + 168 (AssertCommon.swift:171) 1 CoreNFC   0x000000025b99f630 NFCCardSession.startSession() + 296 (NFCCardSession.swift:431) 2 CoreNFC   0x000000025b994771 CardSession.begin() + 1 (CardSession.swift:337) 3 CoreNFC   0x000000025b99427d CardSession.init() + 1 (CardSession.swift:320) 4 Paiement Mobile   0x000000010197f345 HceNativeSDK.startCardSession() + 1
1
0
45
18h
HKWorkoutBuilder.finishWorkout() fails silently (nil workout, nil error) when device is locked (iOS 26.4+)
Hello everyone, We are encountering a critical regression introduced in iOS 26.4 that results in permanent workout data loss for users. When invoking HKWorkoutBuilder.finishWorkout(completion:) while the iOS device is locked, the save operation fails completely. However, it fails silently: the completion handler executes but returns both a nil workout and a nil error. Expected Behavior: Before iOS 26.4 finishWorkout resulted in a workout id, and correctly stored the workout data in HealthKit. According to HealthKit data protection documentation, saving data when the device is locked should either succeed (writing to a temporary journal file to be merged upon unlock) or explicitly throw an error such as HKError.Code.errorDatabaseInaccessible. Actual Behavior: Because the framework returns nil for both the object and the error, the application has no way to detect that the save failed. We cannot implement a retry mechanism or queue the save, resulting in silent data loss. Steps to Reproduce: We have built a Minimal Reproducible Example (MRE) that reliably triggers this: Initialize an HKWorkoutBuilder and call beginCollection(withStart:) followed by endCollection(withEnd:). Wrap the finishWorkout call in a short 5-second asynchronous delay, protected by a UIBackgroundTask to prevent app suspension. Lock the physical device during this 5-second window. The finishWorkout completion handler will execute while the device is locked, returning workout == nil and error == nil. Existing Reports: We have filed this via Feedback Assistant (a month ago) and opened a TSI (a week ago), providing the MRE project and a sysdiagnose captured at the time of failure: Feedback ID: FB22396180 TSI Case-ID: 19755043 As we have not yet received a response or a suggested workaround through these official channels, we are reaching out to the community. Has anyone else encountered this silent failure with HKWorkoutBuilder recently? Any insights or escalation help would be greatly appreciated.
4
1
315
1d
App Not Appearing in App Store Search Results
Hello Apple Developer Support, Our app, GluAI (Apple ID: 6757767664), is currently live and available on the App Store. The direct App Store URL works correctly: https://apps.apple.com/app/id6757767664 However, the app does not appear in App Store search results when searching for the exact app name "GluAI". The app has been live for approximately 3 weeks, so we would appreciate it if you could verify that the app has been properly indexed and is eligible to appear in App Store search results. App Name: GluAI Apple ID: 6757767664
1
0
49
1d
Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
26
12
2.7k
1d
Inconsistent CarPlay Audio Routing: Residual WebKit AudioContext Causes Stuttering in Third-Party Audio Apps via Wireless CarPlay
Environment: OS: iOS 16.0 and later (up to iOS 17.x / 18 beta) Subtopic: CarPlay (Wireless / Wi-Fi & Bluetooth Link) Frameworks: WebKit (WKWebView), AVFAudio (AVAudioSession), CoreAudio Description : We have encountered a critical audio routing and scheduling anomaly specific to Wireless CarPlay environments when a WKWebView leaves a residual AudioContext instance. In our iOS application, we embed an H5 page that utilizes the Web Audio API (AudioContext) to handle audio playback, which includes standard user-interaction-based mute unlocking logic. Under normal conditions (including standalone device playback, Bluetooth A2DP, and Wired CarPlay), if the H5 page is dismissed without explicitly invoking AudioContext.close(), the system handles resource recycling gracefully without side effects. However, exclusively under a Wireless CarPlay connection, if the H5 page is destroyed but the WebKit AudioContext instance remains active or is not explicitly closed by the frontend script, a severe system-level audio scheduling conflict occurs. This anomaly breaks the audio pipeline behavior, causing persistent stuttering, dropped frames, and intermittent audio dropping in concurrent third-party music applications (such as KuGou Music, Spotify, etc.). Observed Behavior & Technical Analysis: Wireless CarPlay Specificity: The issue cannot be reproduced on Wired CarPlay or standard Bluetooth audio routing. This suggests that the CarPlay audio server daemon over Wi-Fi (AirPlay-based transport mechanism) has a different constraint or synchronization mechanism regarding audio graph changes. AudioSession / Audio Graph Contention: It appears that when AudioContext is alive, WebKit maintains an active AVAudioSession or an unreleased node in the system audio graph. When the app switches context or destroys the webview wrapper, the system fails to force-evict or deactivate this residual context under Wireless CarPlay scheduling rules. Resource Starvation for Background Apps: The persistent, phantom audio node induces scheduling friction or thread starvation in the CarPlay audio routing daemon, manifesting as severe buffering/stuttering in whatever third-party audio app currently holds the primary AVAudioSession mixable/non-mixable slot. Questions for Apple Engineers : Root Cause of Wireless CarPlay Routing Discrepancy: Why does the CarPlay audio routing daemon handle unreleased WebKit AudioContext nodes differently over Wireless CarPlay compared to Wired CarPlay and native device endpoints? Is there an underlying lock or stream synchronization issue within the wireless CoreAudio server pipeline? Native iOS Client Side Mitigation/Fallback: Is there an recommended pattern for the native iOS app wrapper (WKWebView container) to forcefully invalidate or tear down WebKit-initiated AudioContext sessions upon view dismissal, ensuring a foolproof fallback even if the H5 frontend fails to call .close() properly? Best Practices for Web Audio + CarPlay Integration: Are there any specific AVAudioSession.CategoryOptions or WebKit configurations we should enforce to prevent a background H5 page from interfering with the system-wide CarPlay audio scheduling? Any insights, workarounds, or documentation pointers from the CoreAudio or CarPlay teams would be greatly appreciated. Thanks!
0
0
61
2d
"In-App Purchases and Subscriptions" section missing from version page — cannot submit subscriptions with binary
I have an iOS app with two auto-renewable subscriptions (monthly and annual) that are fully configured and ready for their first submission. Both products have complete metadata, pricing, localizations, review screenshots, and review notes. The problem: The "In-App Purchases and Subscriptions" section does not appear on the version preparation page. It should appear between "App Review Information" and "App Store Version Release," but it's missing entirely. This means I cannot link the subscriptions to my app version for a combined submission. How I got here: I initially submitted the subscriptions for review independently (via the "Submit for Review" button on the subscription product page), not realizing they needed to be submitted alongside a binary. This resulted in a Guideline 3.1.1 rejection. I then created a new app version with a build, but the "In-App Purchases and Subscriptions" section did not appear on the version page. Not realizing this section should exist, I submitted the app — it was approved and published without the subscriptions. I have since created another new version with a fresh build. The app version, monthly subscription, and yearly subscription are all in "Ready to Submit" state. The section still does not appear. What I've verified: All subscription metadata is complete (pricing, localizations, review screenshots, review notes) Subscription group has a localization A new app version is in "Prepare for Submission" with a build uploaded All business/agreements/tax/banking setup is complete The app has no consumable or non-consumable IAPs — only auto-renewable subscriptions All subscription testing appears to work I've reviewed other forum threads with the same issue (e.g., https://developer.apple.com/forums/thread/778258) and followed all suggestions Environment: App uses StoreKit 2 via Flutter in_app_purchase plugin Two products: monthly and annual auto-renewable subscriptions First-time IAP submission for this app App is currently live on the App Store I opened a Developer Support ticket 7 days ago and have not yet received a resolution. Has anyone encountered this issue and found a workaround? Is there a way to reset the subscription review state so they can be properly linked to a version?
1
0
223
4d
First App Store review submitted after publishing on Google Play 🚀
Hi everyone! Today I finally submitted my first iOS app for App Store review after previously publishing the Android version on Google Play. App ID: 6771439707 The app was developed with Flutter and the process was a very interesting learning experience, especially around: App Privacy configuration screenshots and metadata archive/distribution process App Store Connect setup adapting branding/assets to platform guidelines Coming from Android publishing, I have to admit the Apple review pipeline feels much stricter and more detail-oriented 😄 but also very polished once everything is correctly configured. I just wanted to thank the community because many forum posts helped me solve issues during the submission process. Now waiting for review results 🤞 Greetings from Argentina!
8
0
198
4d
My app is in "Waiting for review" for 10 days
Hi, Hi have released a new app on May 12th, that got reviewed and approved fairly fast (3 days after a single iteration for meta data content). On May 15th, I uploaded an update on the app, improving some feedback and user experience on one of the key features of it. I was expecting a similar delay (1-3 days) but it has been 10 already, and I have not had any contact from apple. My app is related with the World Cup, starting in 15 days, and this delay is working against it ... as I cannot market the app properly until it has the desired update. The submission id is 54d8dd83-8988-499e-964f-222ce9bb4cd3 Is there anyway of getting an answer from Apple on the reason why the review is taking so long?
3
0
144
4d
App Submission Stuck in “Waiting for Review” Since May 21 — No Clear Response from Support
To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and time-sensitive App Review issue to your attention, as my submission has remained in “Waiting for Review” for an unusually long period of time and standard support channels have not yet provided a clear update or resolution. Issue Summary: My app, Cupie, was submitted for review on May 21, 2026. However, the submission has remained in “Waiting for Review” since then and has not moved to “In Review” after several days. I have already submitted an expedited review request and also contacted Apple Support regarding the delay. However, I have not yet received any clear explanation, actionable feedback, or confirmation on whether there is an issue with my account, metadata, build, agreements, or submission queue. Lack of Communication: I have opened the following support cases regarding this issue, but I have not received a meaningful update so far: Case IDs: 102900823761 102901498888 The current lack of communication makes it difficult for me to understand whether my submission is properly queued for review, whether it is stuck, or whether there is any action required from my side. Impact: This is our first public launch submission, and the delay is directly affecting our launch schedule, business operations, and user onboarding plan. We are ready to provide any additional information, test accounts, explanations, or compliance materials required for App Review. Request: I respectfully request that the App Review or Developer Support team help confirm the current status of this submission and clarify whether there is any issue preventing it from moving forward. Specifically, I would appreciate confirmation on the following: Whether my app submission is properly queued for review. Whether there is any issue with my account, metadata, build, agreements, or in-app purchase configuration. Whether the submission is delayed due to additional manual review or review queue congestion. Whether any action is required from my side to proceed. App Name: Cupie - 語音視訊、聊天交友 App ID: 6768550401 Current Status: Waiting for Review Submitted Date: May 21, 2026 Related Case IDs: 102900823761 102901498888 I would sincerely appreciate a prompt update or escalation from an Apple representative, as the submission has been waiting for review for an extended period without clear communication. Thank you for your assistance. Sincerely, Cupie Development Team
1
0
68
4d
App completely stuck in "Waiting for Review" queue for 2 months
Hi everyone, We are experiencing a bizarre issue with one of our apps, BLOKX. Here is the quick timeline: March 26: First submission. No status change for 2 weeks. We canceled and resubmitted. April 27: Still zero movement. We updated our SDK and submitted again on May 15. On the exact same day, we submitted other app from our developer account. It got reviewed and approved. Only BLOKX gets completely ignored. May 20: Suspecting a technical glitch with the specific App ID, we created a brand new App ID and submitted BLOKX as a completely fresh app. Today (May 27): Still stuck in "Waiting for Review" with zero movement. The Support Loop: We have already contacted Apple Support multiple times regarding the old App ID (Case ID: 102871846091 and Case ID: 102875670447). The replies we are getting are incredibly frustrating and factually incorrect. Support keeps replying with a generic template stating that the app “was just submitted today” (matching the exact date of their email reply), completely ignoring the weeks it spent waiting. When we replied back with actual screenshots of our timeline and submission history proving otherwise, they simply copy-pasted the exact same response a few days later, just changing the date to the current day. • App name: BLOKX • Platform: iOS • Current status: Waiting for Review • Total waiting time: Almost 2 months (across both IDs) • Old App ID: 6761107868 • Current App ID: 6771268940 Has anyone faced something similar recently? How did you get Apple to notice? If any Apple engineering or forum moderator can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thanks in advance!
2
0
170
4d
Focusable doesn't work on iPad with external keyboard
I have a custom input view in my app which is .focusable(). It behaves similar to a TextField, where it must be focused in order to be used. This works fine on all platforms including iPad, except when when an external keyboard is connected (magic keyboard), in which case it can't be focused anymore and becomes unusable. Is there a solution to this, or a workaround? My view is very complex, so simple solutions like replacing it with a native view isn't possible, and I must be able to pragmatically force it to focus. Here's a very basic example replicating my issue. Non of the functionality works when a keyboard is connected: struct FocusableTestView: View { @FocusState private var isRectFocused: Bool var body: some View { VStack { // This text field should focus the custom input when pressing return: TextField("Enter text", text: .constant("")) .textFieldStyle(.roundedBorder) .onSubmit { isRectFocused = true } .onKeyPress(.return) { isRectFocused = true return .handled } // This custom "input" should focus itself when tapped: Rectangle() .fill(isRectFocused ? Color.accentColor : Color.gray.opacity(0.3)) .frame(width: 100, height: 100) .overlay( Text(isRectFocused ? "Focused" : "Tap me") ) .focusable(true, interactions: .edit) .focused($isRectFocused) .onTapGesture { isRectFocused = true print("Focused rectangle") } // The focus should be able to be controlled externally: Button("Toggle Focus") { isRectFocused.toggle() } .buttonStyle(.bordered) } .frame(maxWidth: .infinity, maxHeight: .infinity, alignment: .center) } }
2
0
282
4d
App crashes on launch - iOS 26.4.2 - React Native TurboModule bug - Guideline 2.1(a) rejection
Hello Apple Developer community, I am seeking help with a recurring App Store rejection under Guideline 2.1(a) - Performance - App Completeness. My app crashes on launch specifically on iOS 26.4.2 and I have confirmed this is a platform-level bug in React Native — not an issue with my application code. BACKGROUND My app is Highway Exit Food Finder — a navigation utility built with Expo SDK 55 / React Native 0.83. It has been in review for several weeks and has been rejected multiple times due to a crash on launch on iPad Air M3 and iPhone 17 Pro Max running iOS 26.4.2. THE CRASH Every crash log shows the same signature: Exception: EXC_CRASH (SIGABRT) Location: ObjCTurboModule::performVoidMethodInvocation Thread: com.meta.react.turbomodulemanager.queue The crash occurs during TurboModule initialization — BEFORE any JavaScript code runs. This means no application-level code change can fix it. CONFIRMED PLATFORM BUG This crash is documented in: github.com/facebook/react-native/issues/54859 github.com/expo/expo/issues/44680 These issues confirm that React Native's New Architecture TurboModule system throws an NSException during async void method invocation on iOS 26 that cannot be caught, causing SIGABRT. WHAT I HAVE TRIED Removed expo-notifications (possible crash source) Removed react-native-maps Simplified all screens to static components Set newArchEnabled: false in app.json Upgraded to Expo SDK 55 Submitted 17+ builds attempting to fix this Despite all these changes the crash signature remains identical across all builds because the crash happens at the platform level. MY QUESTIONS Has anyone successfully gotten a React Native Expo app approved on App Store Review while running iOS 26.4.2 on review devices? Is there a known working configuration for Expo SDK 55 that avoids the TurboModule crash on iOS 26? Has anyone successfully appealed a 2.1(a) rejection caused by a platform bug rather than app code? Can Apple review devices be updated to use a stable iOS version for reviewing React Native apps while the iOS 26 compatibility issues are resolved? DEVICE AND BUILD INFO Review device: iPad Air 11-inch M3 OS: iPadOS 26.4.2 Framework: Expo SDK 55 / React Native 0.83 Build tool: EAS Build All crash logs reference the identical TurboModule crash signature Any help or guidance from the community or Apple engineers who monitor these forums would be greatly appreciated. Thank you.
2
1
351
4d
NSInvalidArgumentException while sharing in UIDocumentInteractionController
According to our crash analytics, the application crashes when trying to share a PDF file in the UIDocumentInteractionController. This crash takes place on iOS 26+ only. Based on analytics, user sessions end when the pdf file is opened in the UIDocumentInteractionController. We couldn't reproduce it on a physical device or a simulator. Can you please help with a fix or at least workaround for this issue? What's your opinion for bug localization (application or framework)? Crash log is attached below. CoreFoundation __exceptionPreprocess + 164 libobjc.A.dylib objc_exception_throw + 88 CoreFoundation -[__NSArrayM insertObject:atIndex:] + 1276 ShareSheet __79-[SHSheetActivityItemsManager loadItemProvidersForRequest:activity:completion:]_block_invoke + 972 ShareSheet __79-[_UIShareServiceActivityProxy _loadItemProvidersFromActivityItems:completion:]_block_invoke + 88 ShareSheet __74+[UIActivity _loadItemProvidersFromActivityItems:withCacheURL:completion:]_block_invoke_4 + 352 libdispatch.dylib _dispatch_call_block_and_release + 32 libdispatch.dylib _dispatch_main_queue_drain.cold.5 + 812 libdispatch.dylib _dispatch_main_queue_drain + 180 CoreFoundation __CFRunLoopRun + 1944
4
0
324
1w
AVSpeechSynthesisVoice.speechVoices() - different behavior on Mac (Designed for iPhone) and iOS and MANY errors checking .audioFileSettings properties.
We recently started working on getting an iOS app to work on Macs with Apple Silicon as a "Designed for iPhone" app and are having issues with speech synthesis. Specifically, voices retuned by AVSpeechSynthesisVoice.speechVoices() do not all work on the Mac. When we build an utterance and attempt to speak, the synthesizer falls back on a default voice and says some very odd text about voice parameters (that is not in the utterance speech text) before it does say the intended speech. Here is some sample code to setup the utterance and speak: func speak(_ text: String, _ settings: AppSettings) { let utterance = AVSpeechUtterance(string: text) if let voice = AVSpeechSynthesisVoice(identifier: settings.selectedVoiceIdentifier) { utterance.voice = voice print("speak: voice assigned \(voice.audioFileSettings)") } else { print("speak: voice error") } utterance.rate = settings.speechRate utterance.pitchMultiplier = settings.speechPitch do { let audioSession = AVAudioSession.sharedInstance() try audioSession.setCategory(.playback, mode: .default, options: .duckOthers) try audioSession.setActive(true, options: .notifyOthersOnDeactivation) self.synthesizer.speak(utterance) return } catch let error { print("speak: Error setting up AVAudioSession: \(error.localizedDescription)") } } When running the app on the Mac, this is the kind of error we get with "com.apple.eloquence.en-US.Rocko" as the selectedVoiceIdentifier: speak: voice assgined [:] 2023-05-29 18:00:14.245513-0700 A.I.[9244:240554] [aqme] AQMEIO_HAL.cpp:742 kAudioDevicePropertyMute returned err 2003332927 2023-05-29 18:00:14.410477-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.412837-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.413774-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.414661-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.415544-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.416384-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.416804-0700 A.I.[9244:240554] [AXTTSCommon] Audio Unit failed to start after 5 attempts. 2023-05-29 18:00:14.416974-0700 A.I.[9244:240554] [AXTTSCommon] VoiceProvider: Could not start synthesis for request SSML Length: 140, Voice: [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null), converted from tts request [TTSSpeechRequest 0x600002c29590] <speak><voice name="com.apple.eloquence.en-US.Rocko">How much wood would a woodchuck chuck if a wood chuck could chuck wood?</voice></speak> language: en-US footprint: premium rate: 0.500000 pitch: 1.000000 volume: 1.000000 2023-05-29 18:00:14.428421-0700 A.I.[9244:240360] [VOTSpeech] Failed to speak request with error: Error Domain=TTSErrorDomain Code=-4010 "(null)". Attempting to speak again with fallback identifier: com.apple.voice.compact.en-US.Samantha When we run AVSpeechSynthesisVoice.speechVoices(), the "com.apple.eloquence.en-US.Rocko" is absolutely in the list but fails to speak properly. Notice that the line: print("speak: voice assigned \(voice.audioFileSettings)") Shows: speak: voice assigned [:] The .audioFileSettings being empty seems to be a common factor for the voices that do not work properly on the Mac. For voices that do work, we see this kind of output and values in the .audioFileSettings: speak: voice assigned ["AVFormatIDKey": 1819304813, "AVLinearPCMBitDepthKey": 16, "AVLinearPCMIsBigEndianKey": 0, "AVLinearPCMIsFloatKey": 0, "AVSampleRateKey": 22050, "AVLinearPCMIsNonInterleaved": 0, "AVNumberOfChannelsKey": 1] So we added a function to check the .audioFileSettings for each voice returned by AVSpeechSynthesisVoice.speechVoices(): //The voices are set in init(): var voices = AVSpeechSynthesisVoice.speechVoices() ... func checkVoices() { DispatchQueue.global().async { [weak self] in guard let self = self else { return } let checkedVoices = self.voices.map { ($0.0, $0.0.audioFileSettings.count) } DispatchQueue.main.async { self.voices = checkedVoices } } } That looks simple enough, and does work to identify which voices have no data in their .audioFileSettings. But we have to run it asynchronously because on a real iPhone device, it takes more than 9 seconds and produces a tremendous amount of error spew to the console. 2023-06-02 10:56:59.805910-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:56:59.971435-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:57:00.122976-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:57:00.144430-0700 A.I.[17186:910116] [AXTTSCommon] MauiVocalizer: 11006 (Can't compile rule): regularExpression=\Oviedo(?=, (\x1b\\pause=\d+\\)?Florida)\b, message=unrecognized character follows \, characterPosition=1 2023-06-02 10:57:00.147993-0700 A.I.[17186:910116] [AXTTSCommon] MauiVocalizer: 16038 (Resource load failed): component=ttt/re, uri=, contentType=application/x-vocalizer-rettt+text, lhError=88602000 2023-06-02 10:57:00.148036-0700 A.I.[17186:910116] [AXTTSCommon] Error loading rules: 2147483648 ... This goes on and on and on ... There must be a better way?
7
1
3.6k
1w
[macOS 26.4.x, iOS 26.4.x] Handoff broken?
Hello, with macOS' and iOS' recent updates (26.4.x), Handoff in my app appears to have become dysfunctional, as I receive the following message in the logs: getContinuationStreamsWithCompletionHandler(), inputStream=(null) outputStream=(null) error=Error Domain=NSPOSIXErrorDomain Code=94 "Bad message" UserInfo={NSLocalizedDescription=Could not set up internal streams} It ONLY works: From a Mac with 15.x to other Macs or iOS devices (on 26.4.x). All other combinations (see below) do NOT work: iOS (26.4.x) > iOS (26.4.x) iOS (26.4.x) > Mac (26.4.x) iOS (26.4.x) > Mac (15.x) Mac (26.4.x) > iOS (26.4.x) The Handoff prompt is shown in the Dock on Mac, in the app switcher on iOS, and in the Dock on iPadOS, but once I click/press it, I get the continuationStreams error. Now, is it my app, or the OS? Thank you kindly, – Matthias
7
0
461
1w
iOS app stuck in “Waiting for Review” for almost 2 weeks
Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.
1
0
80
1w
Remove iPhone and iPad app availability alone(Not Mac App)
Hi All, We have released our application in both iOs and Mac Os platform. But Now we have changed our plan to target Mac Os only. So, We need to disable the availability of iOs version of our app. As I have checked in 'Pricing And Availability' Page, There is one option to remove from sale. But What we need to do to disable iOs app availability alone(Not Mac app)? Please give your suggestion to do this. Thanks.
1
1
371
1w
Face ID not working in App Store after upgrade from beta iOS 15
I was using the iOS 15 beta on my iPhone 12 Pro Max, long story short after upgrading to the full release of iOS 15, my iPhone will not prompt to use faceid for App Store or iTunes Store purchases. I’ve tried signing in and out of iCloud, disabling and renabling Face ID but no luck. I see others have had this issue since the general release of iOS 15 but no comment has been made by apple support. Any advice on a solution?
1
1
410
1w
Ready for Distribution" status for 17 days - Apple Support unresponsive, need advice
Hello everyone, I'm facing an unusual issue with App Store Connect. My app has been in the "Ready for Distribution" status for over 2 weeks (17 days) now. Normally, distribution starts within a few hours after approval, but in this case nothing happens. What I already did: The app successfully passed the review (status is green / approved). Distribution is set to automatic release (I also tried manual — no difference). I submitted a ticket to Apple Developer Support via the official form few days ago. Ticket number: Case ID: 102898955253 I haven't received any response from Apple so far — not even an automated acknowledgment beyond the initial one. Checked spam/junk folders — no emails from Apple. My question to the community: Has anyone experienced such a long delay in the "Ready for Distribution" state recently? Is there any way to "nudge" the process without waiting for Apple Support? Would re-submitting a new build (incrementing the version number) help reset the state? Any advice would be greatly appreciated. Thank you.
Replies
2
Boosts
0
Views
76
Activity
2h
App Review stuck with no progress or feedback — urgent update blocked
Hello, I’m currently dealing with an App Review situation that has been stuck with no real progress and no useful feedback from Apple. App Name: Juego de Impostor: Palabras Apple ID: 6757995242 Bundle ID: com.rgioia.impostorwords Version: 1.8.0 Current Status: Ready for Review Previous Version: 1.7.0 Ready for Distribution Timeline: The app/update has been waiting for review for an unusually long time. There has been no clear movement, no rejection, no explanation, and no actionable feedback from the review team. This is especially frustrating because this is not a new experimental app or an unclear submission. The app is already prepared for release/update, and I need to push fixes and improvements for users. What I already did: Requested expedited review → approved Contacted Apple Developer Support multiple times Followed up several times Waited without receiving any meaningful update The only response I received was that the expedited review request was accepted, but after that nothing actually happened. Impact: The app/update is completely blocked I cannot release fixes or improvements There is no rejection reason to fix There is no communication from App Review I have no visibility into whether this is a review queue issue, an account issue, or a pipeline problem At this point, this does not feel like a normal App Review delay. It feels like the submission is stuck somewhere internally with no owner and no progress. Questions: Is anyone else experiencing this kind of delay recently? Is there any real way to escalate a stuck App Review case after an expedited review was already approved? Could this indicate an issue with the App Review pipeline or my account/app status? How can I get someone from Apple to actually look into the submission instead of receiving generic support replies? I understand that delays can happen, but having an app/update blocked for this long with no feedback, no rejection, and no progress is not acceptable for developers trying to maintain a live product. Any help, visibility, or escalation path would be appreciated. — Ramiro Gioia
Replies
0
Boosts
0
Views
75
Activity
11h
Crash on CardSession
We are working on an HCE application following your documentation. Almost everything is working fine except that we encounter a crash when using CardSession.init() method. We are calling CardSession.isEligible() before CardSession.init(). This crash is random and affects very few user and we did not find a way yet to reproduce this crash on our side. Our theory is CardSession.isEligible() is doing thing under the hood and make CardSession.init() cause a crash, but that just our theory. Here are some stacks : CoreNFC/NFCCardSession.swift:431: Fatal error: Previous session exists 0 libswiftCore.dylib   0x000000019ed73800 _assertionFailure(_:_:file:line:flags:) + 168 (AssertCommon.swift:171) 1 CoreNFC   0x000000025b99f630 NFCCardSession.startSession() + 296 (NFCCardSession.swift:431) 2 CoreNFC   0x000000025b994771 CardSession.begin() + 1 (CardSession.swift:337) 3 CoreNFC   0x000000025b99427d CardSession.init() + 1 (CardSession.swift:320) 4 Paiement Mobile   0x000000010197f345 HceNativeSDK.startCardSession() + 1
Replies
1
Boosts
0
Views
45
Activity
18h
HKWorkoutBuilder.finishWorkout() fails silently (nil workout, nil error) when device is locked (iOS 26.4+)
Hello everyone, We are encountering a critical regression introduced in iOS 26.4 that results in permanent workout data loss for users. When invoking HKWorkoutBuilder.finishWorkout(completion:) while the iOS device is locked, the save operation fails completely. However, it fails silently: the completion handler executes but returns both a nil workout and a nil error. Expected Behavior: Before iOS 26.4 finishWorkout resulted in a workout id, and correctly stored the workout data in HealthKit. According to HealthKit data protection documentation, saving data when the device is locked should either succeed (writing to a temporary journal file to be merged upon unlock) or explicitly throw an error such as HKError.Code.errorDatabaseInaccessible. Actual Behavior: Because the framework returns nil for both the object and the error, the application has no way to detect that the save failed. We cannot implement a retry mechanism or queue the save, resulting in silent data loss. Steps to Reproduce: We have built a Minimal Reproducible Example (MRE) that reliably triggers this: Initialize an HKWorkoutBuilder and call beginCollection(withStart:) followed by endCollection(withEnd:). Wrap the finishWorkout call in a short 5-second asynchronous delay, protected by a UIBackgroundTask to prevent app suspension. Lock the physical device during this 5-second window. The finishWorkout completion handler will execute while the device is locked, returning workout == nil and error == nil. Existing Reports: We have filed this via Feedback Assistant (a month ago) and opened a TSI (a week ago), providing the MRE project and a sysdiagnose captured at the time of failure: Feedback ID: FB22396180 TSI Case-ID: 19755043 As we have not yet received a response or a suggested workaround through these official channels, we are reaching out to the community. Has anyone else encountered this silent failure with HKWorkoutBuilder recently? Any insights or escalation help would be greatly appreciated.
Replies
4
Boosts
1
Views
315
Activity
1d
App Not Appearing in App Store Search Results
Hello Apple Developer Support, Our app, GluAI (Apple ID: 6757767664), is currently live and available on the App Store. The direct App Store URL works correctly: https://apps.apple.com/app/id6757767664 However, the app does not appear in App Store search results when searching for the exact app name "GluAI". The app has been live for approximately 3 weeks, so we would appreciate it if you could verify that the app has been properly indexed and is eligible to appear in App Store search results. App Name: GluAI Apple ID: 6757767664
Replies
1
Boosts
0
Views
49
Activity
1d
Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
Replies
26
Boosts
12
Views
2.7k
Activity
1d
Inconsistent CarPlay Audio Routing: Residual WebKit AudioContext Causes Stuttering in Third-Party Audio Apps via Wireless CarPlay
Environment: OS: iOS 16.0 and later (up to iOS 17.x / 18 beta) Subtopic: CarPlay (Wireless / Wi-Fi & Bluetooth Link) Frameworks: WebKit (WKWebView), AVFAudio (AVAudioSession), CoreAudio Description : We have encountered a critical audio routing and scheduling anomaly specific to Wireless CarPlay environments when a WKWebView leaves a residual AudioContext instance. In our iOS application, we embed an H5 page that utilizes the Web Audio API (AudioContext) to handle audio playback, which includes standard user-interaction-based mute unlocking logic. Under normal conditions (including standalone device playback, Bluetooth A2DP, and Wired CarPlay), if the H5 page is dismissed without explicitly invoking AudioContext.close(), the system handles resource recycling gracefully without side effects. However, exclusively under a Wireless CarPlay connection, if the H5 page is destroyed but the WebKit AudioContext instance remains active or is not explicitly closed by the frontend script, a severe system-level audio scheduling conflict occurs. This anomaly breaks the audio pipeline behavior, causing persistent stuttering, dropped frames, and intermittent audio dropping in concurrent third-party music applications (such as KuGou Music, Spotify, etc.). Observed Behavior & Technical Analysis: Wireless CarPlay Specificity: The issue cannot be reproduced on Wired CarPlay or standard Bluetooth audio routing. This suggests that the CarPlay audio server daemon over Wi-Fi (AirPlay-based transport mechanism) has a different constraint or synchronization mechanism regarding audio graph changes. AudioSession / Audio Graph Contention: It appears that when AudioContext is alive, WebKit maintains an active AVAudioSession or an unreleased node in the system audio graph. When the app switches context or destroys the webview wrapper, the system fails to force-evict or deactivate this residual context under Wireless CarPlay scheduling rules. Resource Starvation for Background Apps: The persistent, phantom audio node induces scheduling friction or thread starvation in the CarPlay audio routing daemon, manifesting as severe buffering/stuttering in whatever third-party audio app currently holds the primary AVAudioSession mixable/non-mixable slot. Questions for Apple Engineers : Root Cause of Wireless CarPlay Routing Discrepancy: Why does the CarPlay audio routing daemon handle unreleased WebKit AudioContext nodes differently over Wireless CarPlay compared to Wired CarPlay and native device endpoints? Is there an underlying lock or stream synchronization issue within the wireless CoreAudio server pipeline? Native iOS Client Side Mitigation/Fallback: Is there an recommended pattern for the native iOS app wrapper (WKWebView container) to forcefully invalidate or tear down WebKit-initiated AudioContext sessions upon view dismissal, ensuring a foolproof fallback even if the H5 frontend fails to call .close() properly? Best Practices for Web Audio + CarPlay Integration: Are there any specific AVAudioSession.CategoryOptions or WebKit configurations we should enforce to prevent a background H5 page from interfering with the system-wide CarPlay audio scheduling? Any insights, workarounds, or documentation pointers from the CoreAudio or CarPlay teams would be greatly appreciated. Thanks!
Replies
0
Boosts
0
Views
61
Activity
2d
"In-App Purchases and Subscriptions" section missing from version page — cannot submit subscriptions with binary
I have an iOS app with two auto-renewable subscriptions (monthly and annual) that are fully configured and ready for their first submission. Both products have complete metadata, pricing, localizations, review screenshots, and review notes. The problem: The "In-App Purchases and Subscriptions" section does not appear on the version preparation page. It should appear between "App Review Information" and "App Store Version Release," but it's missing entirely. This means I cannot link the subscriptions to my app version for a combined submission. How I got here: I initially submitted the subscriptions for review independently (via the "Submit for Review" button on the subscription product page), not realizing they needed to be submitted alongside a binary. This resulted in a Guideline 3.1.1 rejection. I then created a new app version with a build, but the "In-App Purchases and Subscriptions" section did not appear on the version page. Not realizing this section should exist, I submitted the app — it was approved and published without the subscriptions. I have since created another new version with a fresh build. The app version, monthly subscription, and yearly subscription are all in "Ready to Submit" state. The section still does not appear. What I've verified: All subscription metadata is complete (pricing, localizations, review screenshots, review notes) Subscription group has a localization A new app version is in "Prepare for Submission" with a build uploaded All business/agreements/tax/banking setup is complete The app has no consumable or non-consumable IAPs — only auto-renewable subscriptions All subscription testing appears to work I've reviewed other forum threads with the same issue (e.g., https://developer.apple.com/forums/thread/778258) and followed all suggestions Environment: App uses StoreKit 2 via Flutter in_app_purchase plugin Two products: monthly and annual auto-renewable subscriptions First-time IAP submission for this app App is currently live on the App Store I opened a Developer Support ticket 7 days ago and have not yet received a resolution. Has anyone encountered this issue and found a workaround? Is there a way to reset the subscription review state so they can be properly linked to a version?
Replies
1
Boosts
0
Views
223
Activity
4d
First App Store review submitted after publishing on Google Play 🚀
Hi everyone! Today I finally submitted my first iOS app for App Store review after previously publishing the Android version on Google Play. App ID: 6771439707 The app was developed with Flutter and the process was a very interesting learning experience, especially around: App Privacy configuration screenshots and metadata archive/distribution process App Store Connect setup adapting branding/assets to platform guidelines Coming from Android publishing, I have to admit the Apple review pipeline feels much stricter and more detail-oriented 😄 but also very polished once everything is correctly configured. I just wanted to thank the community because many forum posts helped me solve issues during the submission process. Now waiting for review results 🤞 Greetings from Argentina!
Replies
8
Boosts
0
Views
198
Activity
4d
My app is in "Waiting for review" for 10 days
Hi, Hi have released a new app on May 12th, that got reviewed and approved fairly fast (3 days after a single iteration for meta data content). On May 15th, I uploaded an update on the app, improving some feedback and user experience on one of the key features of it. I was expecting a similar delay (1-3 days) but it has been 10 already, and I have not had any contact from apple. My app is related with the World Cup, starting in 15 days, and this delay is working against it ... as I cannot market the app properly until it has the desired update. The submission id is 54d8dd83-8988-499e-964f-222ce9bb4cd3 Is there anyway of getting an answer from Apple on the reason why the review is taking so long?
Replies
3
Boosts
0
Views
144
Activity
4d
App Submission Stuck in “Waiting for Review” Since May 21 — No Clear Response from Support
To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and time-sensitive App Review issue to your attention, as my submission has remained in “Waiting for Review” for an unusually long period of time and standard support channels have not yet provided a clear update or resolution. Issue Summary: My app, Cupie, was submitted for review on May 21, 2026. However, the submission has remained in “Waiting for Review” since then and has not moved to “In Review” after several days. I have already submitted an expedited review request and also contacted Apple Support regarding the delay. However, I have not yet received any clear explanation, actionable feedback, or confirmation on whether there is an issue with my account, metadata, build, agreements, or submission queue. Lack of Communication: I have opened the following support cases regarding this issue, but I have not received a meaningful update so far: Case IDs: 102900823761 102901498888 The current lack of communication makes it difficult for me to understand whether my submission is properly queued for review, whether it is stuck, or whether there is any action required from my side. Impact: This is our first public launch submission, and the delay is directly affecting our launch schedule, business operations, and user onboarding plan. We are ready to provide any additional information, test accounts, explanations, or compliance materials required for App Review. Request: I respectfully request that the App Review or Developer Support team help confirm the current status of this submission and clarify whether there is any issue preventing it from moving forward. Specifically, I would appreciate confirmation on the following: Whether my app submission is properly queued for review. Whether there is any issue with my account, metadata, build, agreements, or in-app purchase configuration. Whether the submission is delayed due to additional manual review or review queue congestion. Whether any action is required from my side to proceed. App Name: Cupie - 語音視訊、聊天交友 App ID: 6768550401 Current Status: Waiting for Review Submitted Date: May 21, 2026 Related Case IDs: 102900823761 102901498888 I would sincerely appreciate a prompt update or escalation from an Apple representative, as the submission has been waiting for review for an extended period without clear communication. Thank you for your assistance. Sincerely, Cupie Development Team
Replies
1
Boosts
0
Views
68
Activity
4d
App completely stuck in "Waiting for Review" queue for 2 months
Hi everyone, We are experiencing a bizarre issue with one of our apps, BLOKX. Here is the quick timeline: March 26: First submission. No status change for 2 weeks. We canceled and resubmitted. April 27: Still zero movement. We updated our SDK and submitted again on May 15. On the exact same day, we submitted other app from our developer account. It got reviewed and approved. Only BLOKX gets completely ignored. May 20: Suspecting a technical glitch with the specific App ID, we created a brand new App ID and submitted BLOKX as a completely fresh app. Today (May 27): Still stuck in "Waiting for Review" with zero movement. The Support Loop: We have already contacted Apple Support multiple times regarding the old App ID (Case ID: 102871846091 and Case ID: 102875670447). The replies we are getting are incredibly frustrating and factually incorrect. Support keeps replying with a generic template stating that the app “was just submitted today” (matching the exact date of their email reply), completely ignoring the weeks it spent waiting. When we replied back with actual screenshots of our timeline and submission history proving otherwise, they simply copy-pasted the exact same response a few days later, just changing the date to the current day. • App name: BLOKX • Platform: iOS • Current status: Waiting for Review • Total waiting time: Almost 2 months (across both IDs) • Old App ID: 6761107868 • Current App ID: 6771268940 Has anyone faced something similar recently? How did you get Apple to notice? If any Apple engineering or forum moderator can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thanks in advance!
Replies
2
Boosts
0
Views
170
Activity
4d
Focusable doesn't work on iPad with external keyboard
I have a custom input view in my app which is .focusable(). It behaves similar to a TextField, where it must be focused in order to be used. This works fine on all platforms including iPad, except when when an external keyboard is connected (magic keyboard), in which case it can't be focused anymore and becomes unusable. Is there a solution to this, or a workaround? My view is very complex, so simple solutions like replacing it with a native view isn't possible, and I must be able to pragmatically force it to focus. Here's a very basic example replicating my issue. Non of the functionality works when a keyboard is connected: struct FocusableTestView: View { @FocusState private var isRectFocused: Bool var body: some View { VStack { // This text field should focus the custom input when pressing return: TextField("Enter text", text: .constant("")) .textFieldStyle(.roundedBorder) .onSubmit { isRectFocused = true } .onKeyPress(.return) { isRectFocused = true return .handled } // This custom "input" should focus itself when tapped: Rectangle() .fill(isRectFocused ? Color.accentColor : Color.gray.opacity(0.3)) .frame(width: 100, height: 100) .overlay( Text(isRectFocused ? "Focused" : "Tap me") ) .focusable(true, interactions: .edit) .focused($isRectFocused) .onTapGesture { isRectFocused = true print("Focused rectangle") } // The focus should be able to be controlled externally: Button("Toggle Focus") { isRectFocused.toggle() } .buttonStyle(.bordered) } .frame(maxWidth: .infinity, maxHeight: .infinity, alignment: .center) } }
Replies
2
Boosts
0
Views
282
Activity
4d
App crashes on launch - iOS 26.4.2 - React Native TurboModule bug - Guideline 2.1(a) rejection
Hello Apple Developer community, I am seeking help with a recurring App Store rejection under Guideline 2.1(a) - Performance - App Completeness. My app crashes on launch specifically on iOS 26.4.2 and I have confirmed this is a platform-level bug in React Native — not an issue with my application code. BACKGROUND My app is Highway Exit Food Finder — a navigation utility built with Expo SDK 55 / React Native 0.83. It has been in review for several weeks and has been rejected multiple times due to a crash on launch on iPad Air M3 and iPhone 17 Pro Max running iOS 26.4.2. THE CRASH Every crash log shows the same signature: Exception: EXC_CRASH (SIGABRT) Location: ObjCTurboModule::performVoidMethodInvocation Thread: com.meta.react.turbomodulemanager.queue The crash occurs during TurboModule initialization — BEFORE any JavaScript code runs. This means no application-level code change can fix it. CONFIRMED PLATFORM BUG This crash is documented in: github.com/facebook/react-native/issues/54859 github.com/expo/expo/issues/44680 These issues confirm that React Native's New Architecture TurboModule system throws an NSException during async void method invocation on iOS 26 that cannot be caught, causing SIGABRT. WHAT I HAVE TRIED Removed expo-notifications (possible crash source) Removed react-native-maps Simplified all screens to static components Set newArchEnabled: false in app.json Upgraded to Expo SDK 55 Submitted 17+ builds attempting to fix this Despite all these changes the crash signature remains identical across all builds because the crash happens at the platform level. MY QUESTIONS Has anyone successfully gotten a React Native Expo app approved on App Store Review while running iOS 26.4.2 on review devices? Is there a known working configuration for Expo SDK 55 that avoids the TurboModule crash on iOS 26? Has anyone successfully appealed a 2.1(a) rejection caused by a platform bug rather than app code? Can Apple review devices be updated to use a stable iOS version for reviewing React Native apps while the iOS 26 compatibility issues are resolved? DEVICE AND BUILD INFO Review device: iPad Air 11-inch M3 OS: iPadOS 26.4.2 Framework: Expo SDK 55 / React Native 0.83 Build tool: EAS Build All crash logs reference the identical TurboModule crash signature Any help or guidance from the community or Apple engineers who monitor these forums would be greatly appreciated. Thank you.
Replies
2
Boosts
1
Views
351
Activity
4d
NSInvalidArgumentException while sharing in UIDocumentInteractionController
According to our crash analytics, the application crashes when trying to share a PDF file in the UIDocumentInteractionController. This crash takes place on iOS 26+ only. Based on analytics, user sessions end when the pdf file is opened in the UIDocumentInteractionController. We couldn't reproduce it on a physical device or a simulator. Can you please help with a fix or at least workaround for this issue? What's your opinion for bug localization (application or framework)? Crash log is attached below. CoreFoundation __exceptionPreprocess + 164 libobjc.A.dylib objc_exception_throw + 88 CoreFoundation -[__NSArrayM insertObject:atIndex:] + 1276 ShareSheet __79-[SHSheetActivityItemsManager loadItemProvidersForRequest:activity:completion:]_block_invoke + 972 ShareSheet __79-[_UIShareServiceActivityProxy _loadItemProvidersFromActivityItems:completion:]_block_invoke + 88 ShareSheet __74+[UIActivity _loadItemProvidersFromActivityItems:withCacheURL:completion:]_block_invoke_4 + 352 libdispatch.dylib _dispatch_call_block_and_release + 32 libdispatch.dylib _dispatch_main_queue_drain.cold.5 + 812 libdispatch.dylib _dispatch_main_queue_drain + 180 CoreFoundation __CFRunLoopRun + 1944
Replies
4
Boosts
0
Views
324
Activity
1w
AVSpeechSynthesisVoice.speechVoices() - different behavior on Mac (Designed for iPhone) and iOS and MANY errors checking .audioFileSettings properties.
We recently started working on getting an iOS app to work on Macs with Apple Silicon as a "Designed for iPhone" app and are having issues with speech synthesis. Specifically, voices retuned by AVSpeechSynthesisVoice.speechVoices() do not all work on the Mac. When we build an utterance and attempt to speak, the synthesizer falls back on a default voice and says some very odd text about voice parameters (that is not in the utterance speech text) before it does say the intended speech. Here is some sample code to setup the utterance and speak: func speak(_ text: String, _ settings: AppSettings) { let utterance = AVSpeechUtterance(string: text) if let voice = AVSpeechSynthesisVoice(identifier: settings.selectedVoiceIdentifier) { utterance.voice = voice print("speak: voice assigned \(voice.audioFileSettings)") } else { print("speak: voice error") } utterance.rate = settings.speechRate utterance.pitchMultiplier = settings.speechPitch do { let audioSession = AVAudioSession.sharedInstance() try audioSession.setCategory(.playback, mode: .default, options: .duckOthers) try audioSession.setActive(true, options: .notifyOthersOnDeactivation) self.synthesizer.speak(utterance) return } catch let error { print("speak: Error setting up AVAudioSession: \(error.localizedDescription)") } } When running the app on the Mac, this is the kind of error we get with "com.apple.eloquence.en-US.Rocko" as the selectedVoiceIdentifier: speak: voice assgined [:] 2023-05-29 18:00:14.245513-0700 A.I.[9244:240554] [aqme] AQMEIO_HAL.cpp:742 kAudioDevicePropertyMute returned err 2003332927 2023-05-29 18:00:14.410477-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.412837-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.413774-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.414661-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.415544-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.416384-0700 A.I.[9244:240554] Could not retrieve voice [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null) 2023-05-29 18:00:14.416804-0700 A.I.[9244:240554] [AXTTSCommon] Audio Unit failed to start after 5 attempts. 2023-05-29 18:00:14.416974-0700 A.I.[9244:240554] [AXTTSCommon] VoiceProvider: Could not start synthesis for request SSML Length: 140, Voice: [AVSpeechSynthesisProviderVoice 0x6000033794f0] Name: Rocko, Identifier: com.apple.eloquence.en-US.Rocko, Supported Languages ( "en-US" ), Age: 0, Gender: 0, Size: 0, Version: (null), converted from tts request [TTSSpeechRequest 0x600002c29590] <speak><voice name="com.apple.eloquence.en-US.Rocko">How much wood would a woodchuck chuck if a wood chuck could chuck wood?</voice></speak> language: en-US footprint: premium rate: 0.500000 pitch: 1.000000 volume: 1.000000 2023-05-29 18:00:14.428421-0700 A.I.[9244:240360] [VOTSpeech] Failed to speak request with error: Error Domain=TTSErrorDomain Code=-4010 "(null)". Attempting to speak again with fallback identifier: com.apple.voice.compact.en-US.Samantha When we run AVSpeechSynthesisVoice.speechVoices(), the "com.apple.eloquence.en-US.Rocko" is absolutely in the list but fails to speak properly. Notice that the line: print("speak: voice assigned \(voice.audioFileSettings)") Shows: speak: voice assigned [:] The .audioFileSettings being empty seems to be a common factor for the voices that do not work properly on the Mac. For voices that do work, we see this kind of output and values in the .audioFileSettings: speak: voice assigned ["AVFormatIDKey": 1819304813, "AVLinearPCMBitDepthKey": 16, "AVLinearPCMIsBigEndianKey": 0, "AVLinearPCMIsFloatKey": 0, "AVSampleRateKey": 22050, "AVLinearPCMIsNonInterleaved": 0, "AVNumberOfChannelsKey": 1] So we added a function to check the .audioFileSettings for each voice returned by AVSpeechSynthesisVoice.speechVoices(): //The voices are set in init(): var voices = AVSpeechSynthesisVoice.speechVoices() ... func checkVoices() { DispatchQueue.global().async { [weak self] in guard let self = self else { return } let checkedVoices = self.voices.map { ($0.0, $0.0.audioFileSettings.count) } DispatchQueue.main.async { self.voices = checkedVoices } } } That looks simple enough, and does work to identify which voices have no data in their .audioFileSettings. But we have to run it asynchronously because on a real iPhone device, it takes more than 9 seconds and produces a tremendous amount of error spew to the console. 2023-06-02 10:56:59.805910-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:56:59.971435-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:57:00.122976-0700 A.I.[17186:910118] [catalog] Query for com.apple.MobileAsset.VoiceServices.VoiceResources failed: 2 2023-06-02 10:57:00.144430-0700 A.I.[17186:910116] [AXTTSCommon] MauiVocalizer: 11006 (Can't compile rule): regularExpression=\Oviedo(?=, (\x1b\\pause=\d+\\)?Florida)\b, message=unrecognized character follows \, characterPosition=1 2023-06-02 10:57:00.147993-0700 A.I.[17186:910116] [AXTTSCommon] MauiVocalizer: 16038 (Resource load failed): component=ttt/re, uri=, contentType=application/x-vocalizer-rettt+text, lhError=88602000 2023-06-02 10:57:00.148036-0700 A.I.[17186:910116] [AXTTSCommon] Error loading rules: 2147483648 ... This goes on and on and on ... There must be a better way?
Replies
7
Boosts
1
Views
3.6k
Activity
1w
[macOS 26.4.x, iOS 26.4.x] Handoff broken?
Hello, with macOS' and iOS' recent updates (26.4.x), Handoff in my app appears to have become dysfunctional, as I receive the following message in the logs: getContinuationStreamsWithCompletionHandler(), inputStream=(null) outputStream=(null) error=Error Domain=NSPOSIXErrorDomain Code=94 "Bad message" UserInfo={NSLocalizedDescription=Could not set up internal streams} It ONLY works: From a Mac with 15.x to other Macs or iOS devices (on 26.4.x). All other combinations (see below) do NOT work: iOS (26.4.x) > iOS (26.4.x) iOS (26.4.x) > Mac (26.4.x) iOS (26.4.x) > Mac (15.x) Mac (26.4.x) > iOS (26.4.x) The Handoff prompt is shown in the Dock on Mac, in the app switcher on iOS, and in the Dock on iPadOS, but once I click/press it, I get the continuationStreams error. Now, is it my app, or the OS? Thank you kindly, – Matthias
Replies
7
Boosts
0
Views
461
Activity
1w
iOS app stuck in “Waiting for Review” for almost 2 weeks
Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.
Replies
1
Boosts
0
Views
80
Activity
1w
Remove iPhone and iPad app availability alone(Not Mac App)
Hi All, We have released our application in both iOs and Mac Os platform. But Now we have changed our plan to target Mac Os only. So, We need to disable the availability of iOs version of our app. As I have checked in 'Pricing And Availability' Page, There is one option to remove from sale. But What we need to do to disable iOs app availability alone(Not Mac app)? Please give your suggestion to do this. Thanks.
Replies
1
Boosts
1
Views
371
Activity
1w
Face ID not working in App Store after upgrade from beta iOS 15
I was using the iOS 15 beta on my iPhone 12 Pro Max, long story short after upgrading to the full release of iOS 15, my iPhone will not prompt to use faceid for App Store or iTunes Store purchases. I’ve tried signing in and out of iCloud, disabling and renabling Face ID but no luck. I see others have had this issue since the general release of iOS 15 but no comment has been made by apple support. Any advice on a solution?
Replies
1
Boosts
1
Views
410
Activity
1w