“We are unable to process your request”

[Reply to DTS Engineer] Thank you for looking into this. I have identified the root cause of the issue: it is a Bundle ID case-sensitivity mismatch. My parent app was approved as com.hayashikento.FocusPact (Capitalized), but I accidentally requested the Configuration Extension with a lowercase ID (com.hayashikento.focuspact...). This causes a Prefix Mismatch error in Xcode, preventing me from archiving the app. To fix this, I have just submitted a new entitlement request with the corrected capitalized ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Since the core functionality was already approved under the lowercase ID, could you please expedite the approval for this capitalized version? This technical correction is the only thing blocking my TestFlight distribution. Thank you for your support!

Thank you for the suggestion. I monitored the system log from the ecosystemd process as you recommended. Here are the relevant log entries I found when launching VLC: ecosystemd: [GAME_CHECK] type=process bundle=org.videolan.vlc result=notGame uid=505 ecosystemd: shouldNotify check: true for ecosystemd: Scheduling notification check for uid: 505 in 2 seconds ecosystemd: detectArchitectures: macho_for_each_slice failed with code 1 for: ecosystemd: Process excluded, skip adding Could you tell me whether these log entries indicate the reason the warning dialog was not displayed, and whether this is a known bug in macOS Tahoe 26.4 beta?

Hello, Our app has been in the Waiting for Review status since Tuesday, March 17th. Typically, our submissions are reviewed within 24–48 hours, so this extended delay is unusual for us. We also submitted an expedited review request, but there has been no update or progress on the review so far. We'd really appreciate any assistance in moving this forward.

Cancel and resubmit the review request.

Yes, this has happened to me more than once not only this week, Cancel and resubmit the review request. This worked for me instead of waiting more than 3 days.

I replied to you in another post. Cancel and resubmit the review request. This worked for me instead of waiting more than 3 days.

Cancel and resubmit the review request. This worked for me instead of waiting more than 3 days.

This is actually possible, though it requires a different approach than the typical single-AVAudioEngine setup. The key insight is that iOS allows multiple AVCaptureSession instances to coexist under certain conditions. You can configure two separate audio routes: Use AVCaptureSession with the AirPods as the input device for your speech recognition pipeline. Set the audio session category to .playAndRecord with .allowBluetooth option. For video recording with the built-in mic, use a second AVCaptureSession (or the camera API you are already using). The built-in mic can be explicitly selected as the audio input for this session. The catch is you need to manage the audio session category carefully. The .mixWithOthers option is essential here — without it, one session will interrupt the other. Another approach that avoids the dual-session complexity: use a single AVCaptureSession that captures from the built-in mic for video, and run SFSpeechRecognizer (or the new SpeechAnalyzer on macOS 26 / iOS 26) on the same