“testflight the requested app is not avaliable”

It’s hard to offer a specific answer without more context. iOS uses many different cryptographic algorithms, and the exact details vary based on the circumstances. Have you read Apple Platform Security? If not, I suggest you start there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

For me, the issue is NOT resolved in Xcode 26.5 beta. I downloaded it and created a 26.5 simulator, but I can NOT paste into it from macOS 26.4 host.

Using Xcode 26.5 Beta with iOS Simulator 26.5 Beta (iPhone 17 Pro), I tried to copy and paste text to the simulator. The paste menu now appears, but cannot paste the text. When pasting the text to the UITextField in my application while debugging, Xcode shows the following error ...requesting item failed with error: Error Domain=PBErrorDomain Code=13 Operation not authorized. UserInfo={NSLocalizedDescription=Operation not authorized.}

I've hit a very similar issue with CoreML model loading hanging on the MLE5ProgramLibrary.lazyInitQueue after OS updates. A few things that helped me work around it: 1. Pre-compile to .mlmodelc instead of loading .mlpackage at runtime The AOT recompilation path (which is what's hanging) gets triggered when the on-device compiled cache is invalidated by the OS update. If you ship a pre-compiled .mlmodelc built with the matching Xcode/SDK version, it often skips recompilation entirely: // Compile once at build time or first launch let compiledURL = try MLModel.compileModel(at: mlpackageURL) // Then load from compiled let model = try MLModel(contentsOf: compiledURL, configuration: config) 2. Load on a background thread with a timeout Since the hang is on a serial dispatch queue and the C++ exception bypasses Swift error handling, wrapping the load in a Task with a timeout at least lets you fail gracefully instead of getting watchdog-killed: let loadTask = Task { try MLModel(contentsOf: modelURL, configuration: c

@DTS Engineer But when I disable the content filter, the process does not stop. When I restart the content filter, it is still the original process instance. When I manually kill the original process, or even reload the new system extension through the wrapper app, the process ID definitely changes, but the issue persists. The only solution I have found so far is to restart the system.

The background like: We have a VoIP app with more call features. Sometimes, we received some feedbacks about call ened. After checking the log file, it shows there are user actions (eg, from func provider(_ provider: CXProvider, perform action: CXEndCallAction)), But the user said no user actions. So we doubt if there is a system-level event or error that will end this call. Then the details of the end call reason would be very helpful for debugging.

Update: I've reverted to using Claude in the Terminal. The implementation in Xcode 26.4 is just so godawful buggy that it's unusable. (I've discovered that if you quit and restart Xcode, the chat history suddenly contains TONS of text that wasn't showing up previously!) Whatever the reason, Xcode 26.4 is just crippled. I haven't tested the new 26.5 beta because you can't ship apps from it yet.

Thanks for looking into this. Here is a complete summary of our setup and what we have confirmed so far. App configuration: macOS app distributed via Developer ID (PKG installer) — not the Mac App Store Host app runs as a menu bar agent (LSUIElement = YES in Info.plist) NSApplicationActivationPolicy = .accessory The app runs continuously as a login item — it is always alive Network Extension is a System Extension (NEAppProxyProvider), always running alongside the host app What we have implemented: MXMetricManager.shared().addSubscriber(self) is called in applicationDidFinishLaunching in the host app — as early as possible A separate MXMetricManagerSubscriber is registered inside the Network Extension process at tunnel start Both didReceiveMetricPayloads: and didReceiveDiagnosticPayloads: are implemented On startup we also drain pastPayloads and pastDiagnosticPayloads to catch anything queued while the process was not running The

Hi Ziqiao, Thank you for confirming the issue. I've filed a Feedback Report as suggested: FB22384792 I'm also experiencing this on Apple Watch Ultra 2 with the latest watchOS. My configuration matches the documentation exactly (WKBackgroundModes with underwater-depth, WKSupportsAutomaticDepthLaunch = true, shallow depth entitlement). I've referenced the original thread (https://developer.apple.com/forums/thread/773542) and feedback report FB16448625 in my submission. Would appreciate any updates from the watchOS team. This is blocking a key feature for our freediving app launch. Thanks, Alexis