Facing this issue since Xcode 13 betas. Disabling Bluetooth in the iPhone temporarily fixes the issue for me. With the Control Center Bluetooth icon in grey, no need to fully disable it in the Settings app.

For what it's worth, the reported feedback ID is FB10006890.

Turns out it was a missing certificate (and private key) for signing the binaries, result of migrating from one Mac to another. Odd the distribution assistant did not warn about that.

Same issue here. Any update?

Seems like that. In my case I received various reports: iPad14,3 reached 4294.97 writes iPad7,2, iPad8,7 and iPhone13,4 all reached 1073.74 writes Nut sure if it is version dependant or maybe storage size dependant but the limit can change. I've just asked for code-level support to Apple, will update with the response.

For what is worth it started working after a few weeks with no further actions on my end. So maybe they review/activate those manually on their part? Not sure but my advice: patience.

I was welcomed with this issue today. Been publishing this app properly signed for years. It's even visible in the package review that the binaries have this flag enabled but the build is being blocked with this message: ITMS-90296: App sandbox not enabled The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[com.aone.keka.pkg/Payload/Keka.app/Contents/MacOS/keka7z ...

+1, feedback sent

Similar to https://developer.apple.com/forums/thread/705472, I had to create new certificates and resign all binaries. Probably this was caused by an expired certificate.

4 years later. I'm filling a feature request in the Feedback Assistant. Please consider doing the same if you want this to be fixed.

Same here, Xcode 15.0.1, macOS 13.6.1 🥲

For macOS 13.0 and iPadOS 16.0 or newer you can use onContinuousHover, although it does not seem to work with the mouse button held down. public func onContinuousHover(coordinateSpace: CoordinateSpace = .local, perform action: @escaping (HoverPhase) -> Void) -> some View

Not really, just a template about how to symbolicate and read crash logs. I'm going to contact them again, since I failed to reply the last time and this is still a big issue. Since the last time, I'm now seeing a new limit of 17.18 GB. The lower end device that reported the issue is an iPhone 13 that has a maximum of 512 GB and on the newer side an iPhone 14 Pro Max that has a minimum of 128 GB, so between 128 - 512 we can get that limit. This means nothing, really, since the 1073 MB limit was reported from an iPhone 15 Pro Max that has at least 256 GB.

To be clear, a good solution for this will be to get something similar to UIApplication.didReceiveMemoryWarningNotification so we can at least prevent the crash and cancel the operation with an explanation to the user.

Sorry Quinn didn't received the notification about the new post. I remember reproducing the crash before but I'll try to reproduce it again tomorrow just to be sure. If you say it does not terminate the app that must be the case, and if it's so, then this is not an issue in cases where the app should be doing that disk intensive tasks. I'm unable to attach a zip here so I've uploaded some xcdiskwritepoint containing the logs: https://d.keka.io/xcdiskwritepoint.zip Thanks for taking the time.