“testflight the requested app is not avaliable”

Hello, We have a security solution which intercepts network traffic for inspection using a combination of Transparent Proxy Provider and Content filter. Lately we are seeing reports from the market that on M5 Macbooks and A18 Neos the system will kernel panic using our solution, even though it never happens on M1-M4 and no significant code changes were made in the mean time. All crashes seem to be related to an internal double free in the kernel: panic(cpu 0 caller 0xfffffe003bb68224): skmem_slab_free_locked: attempt to free invalid or already-freed obj 0xf2fffe29e15f2400 on skm 0xf6fffe2518aaa200 @skmem_slab.c:646 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 25D2128 Kernel version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:54:38 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T6050 Additionally, from further log inspection, before panics we find some weird kernel messages which seem to be related to some DMA operations gone wrong in the network driver on some machines: 2

Hello, app name: raw films app id: 6761117809 I need some help or guidance. I submitted my app on 25 of March and it got rejected due to guideline 2.1b, the reviewer couldn’t locate the button to unlock the premium filters with in-app purchase. I provided them screenshots and exact steps to locate the filters on 26 of March, and no response since then. I resubmitted the app on 30th of March, but still no response in App Store Connect messages, I requested help from support via email, but again no response. :( Can anyone help me with an advice? Thank you..

I cannot find anywhere in the documentation how to invalidate an FSItem. It seems to be cached indefinitely or am I missing something?

I've been stuck on Guideline 2.3 for two weeks now and I'm running out of ideas. My app is iPhone-only (UIDeviceFamily = [1]) and has been on the App Store since January. Version 2.1.9 passed review fine. The only change in 2.1.10 is adding two DeviceActivity extensions — a DeviceActivityMonitor and a DeviceActivityReport — for screen time-based stress detection. Every build since then gets rejected with the same message: The UIRequiredDeviceCapabilities key in the Info.plist is set up in such a way that the app will not install on the device used in review. Review devices: iPhone 14 Pro, iPhone 17 Pro Max, iPad Air M3. Here's what I've tried across 13+ submissions: UIRequiredDeviceCapabilities as [arm64] (array) — rejected Empty array [] — rejected Removed the key entirely — upload validation fails, Xcode re-injects arm64 anyway Post-build script to force [arm64] — rejected Dictionary format {arm64: true} — rejected Added com.apple.developer.family-controls to extension en

Hello. I have a question regarding the standard iPadOS Books app. When I try to open a PDF in the standard iPadOS Books app using the sharing function from another app that works offline, the Books app displays the message, Your iPad is offline. Books could not connect to the Bookstore. Please check your internet connection and try again, and I am unable to open the PDF. Can this problem be resolved by modifying the other app that works offline? Or is this a problem with the Books app itself?

Hello, I have been waiting for a response for 7 days now, I have resubmitted my app (photo editing app) for review. First my app was declined due to guideline 2.1(b), stating that they cannot find a filter with a lock button to test the in app-purchase. I have sent a screenshot for the reviewers and exact steps how to find those filters, this was last Thursday and still haven't received a response. I also sent a support request on Monday (30th of March), but still no response. Can you please help me with an advice? Thank you in advance.

About a year ago, I developed and released an app on the App Store (I believe it was running on the Sequoia SDK at the time), and everything was working fine. I’m now revisiting the project using the newer Tahoe SDK, and I’m running into an issue with DiffableDataSource. Specifically, the app hangs and CPU usage spikes to 100% when applying snapshots. Has anyone experienced similar issues after upgrading to newer SDKs? Are there any recent changes or pitfalls with DiffableDataSource (e.g., threading, Hashable requirements, or snapshot handling) that I should be aware of? Any insights or suggestions would be greatly appreciated. extension Section { enum Identifier: Int, CaseIterable { case main } enum Item: Hashable { case file(FileViewData) } } struct FileViewData: Equatable, Hashable, Identifiable { let id: String let name: String var accessoryViewData: KTFDownloadAccessoryViewData init( id: String, name: String, accessoryViewData: KTFDownloadAccessoryViewData = .nothing ) { self.i

These days I've observed a strange behavior in my document-based app on macOS: Its NSDocument class implementation is overwriting saveToURL:ofType:forSaveOperation:completionHandler:, performing some additional checks and calling super by passing the original parameters. As my app is supporting various file formats for writing (and exporting those UTIs) the user can open a file in one format and save it to another. NSDocument is calling the mentioned methods implicitly after completing the Save as... dialog. If this happens, the passed-on fileType is still the one of format #1, although the file is saved with the file name extension of format #2. This hick-up is not directly obvious to the user. But if the file is re-saved (e.g. after modifications), Cocoa is trying to extend the sandbox for the URL of type #1, and fails with the following error message at the Xcode console: -[STBDocument saveToURL:ofType:forSaveOperation:completionHandler:] [Line 521] typeName: com.janome.jef -[STB