We are using a vendor-provided SDK to access their hardware through EA framework and intermittently the EA framework streams stop working (in particular, the input stream reports 0 for hasAvailableBytes). In some cases, this situation persists until we detach the device and reattach (this is via a lightning connector). After installing the IAPD debug profile and retrieving logs, we notice a few interesting log entries from the syslog we retrieve off the tablet. I am trying to understand and make sense of this and determine how this can be fixed. Anyone have a clue? default 2021-08-20 19:49:09.299659 +0300 accessoryd ERROR: iAP2LinkDeviceActionSendRST: iAP2 Link Layer reset triggered! (state: 5) default 2021-08-20 19:49:11.342001 +0300 accessoryd ERROR: iAP2LinkQueueSendDataWithSentCallback:4410 ERROR: Invalid session(0)! error 2021-08-20 19:49:11.342005 +0300 accessoryd Unable to queue 30 ea bytes for eaSession 50 default 2021-08-20 19:49:12.806935 +0300 Tablet [C1143] event: client:data_stall @3.486s info 2021-08-20 19:49:12.809195 +0300 Tablet nw_connection_report_symptom_on_nw_queue [C1143] reported Data stall symptom

I recently discovered that CryptokenKit (TKSmartCard.transmit) throws an ObjC exception, and thus crashes a Swift app using TKSmartCard (absent an ObjC wrapper to handle the Objc exception explicitly). That was surprising, as there was no documentation indicating that TKSmartCard needs to be wrapped in ObjC instead being used directly from Swift. (See https://developer.apple.com/documentation/cryptotokenkit/tksmartcard/1390161-transmit) - the exception is a NSInternalInconsistencyException, which is thrown when certain codepaths are executed in a certain sequence (which indeed, leaves a TKSmartCard in an inconsistent state). Is there a list of Frameworks that throw ObjC exceptions (and therefore need special handling by Swift when invoking methods/functions)?

I have been investigating a recent breakage where apps being installed via Testflight are crashing on launch with no helpful crash reports, or even console-accessible logging. More detail: The app launches just fine on iPadOS 18 beta (ipad) but the same build doesn't work on iPadOS 17.6.1 At my wit's end, I checked the entire build environment - was I using XCode beta still somewhere? Well, in the XCode Cloud workflow, I had selected "Release" for the latest released version of XCode. And MUCH to my surprise, I see that XCode 16 RC is selected. Why? That's not released yet... Anyway, this is just a friendly PSA to check your XCode Cloud workflows if you choose "release" when new XCode releases are upcoming... or peg your XCode Cloud environment versions. And I still don't have an explanation why Testflight XCode 16 RC is producing builds that crash on iPadOS 17.6.1 (for us) but not the latest iPadOS 18 public beta...