I'm still having this problem. It's probably been a month. Going to this very page in chrome gives me the error mentioned above. Is there some workaround to access dev forums on Chrome? I do everything else in Chrome (including App Store connect, credentials/provisioning, etc)

Two things: It is still happening on my MacBook Pro with Chrome (updated chrome, Monterey 12.4) - I note that the cookie header (in the request to developer.applet.com ) is 6308 bytes (!!) in length. I'm sure this is the immediate cause of the complaint being generated. When I use incognito mode, the error is not present. On Safari, the cookie header is 1324 bytes in length I am a frequent user of apple products/services using multiple accounts. Maybe this is related? I'm happy to help debug this issue @eskimo - I find it terribly annoying (to put it mildly).

OK, well, it turns out we were simply loading the device's GPU (via an in-app WKWebView - we saw numerous ), and under load the EA Framework (accessoryd) appears to display erratic behavior (including it seems, crashing/restarting). We haven't seen these symptoms in a while, but just for the record, this is how we finally addressed this issue.

Yah, this happens every time I access developer.apple.com but only /forums -- I do appstoreconnect,the top level /account tools, etc all the time on chrome and never see this issue. It really seems scoped to /forums for me. Doesn't matter if I restart Chrome. I haven't cleared cookies - I'm sure that will make it work for a short period of time, and then the issue returns. I have multiple profiles on Chrome but I really only ever use the one I am using now and see this problem.

Yah, this continues to be a problem. I still can't use Chrome to access developer forums. Any update?

Hi Quinn- I'm not trying to understand why its throwing the ObjC exception (though i wish it was a Swift error, because in the case of the card state, it really is recoverable, I think) - I'm trying to figure out what methods/functions are going to throw exceptions, and how to properly handle it, from a Swift app. Maybe TKSmartCard is not following the guidelines about throwing exceptions? Another example I just saw today:TKSmartCardSlotManager. slotNames threw this ObjC exception (during awakening from background, seen once): SIGABRT (#0): Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <__NSDictionaryM: 0x300f8c860> was mutated while being enumerated.'. I'm guessing there's something happening on resuming from background in the framework that is causing a race condition. I notice that in another thread in the crash report there's something suspicious (this is not a method that is publicly available - I don't know how it gets called): 4 CryptoTokenKit 0x00000001cc7d2934 -[TKSmartCardSlotManager setSlotWithName:endpoint:type:reply:] + 276 The question I am asking is about to what extent we are supposed to be writing ObjC wrappers around Frameworks like TKSmartCard instead of calling the TKSmartCard framework functions directly from Swift, since TKSmartCard seems to be throwing some ObjC exceptions in places I find surprising. P.S. It feels like you are holding up the entire developer ecosystem on your shoulders, I hope your effort it recognized by Apple. Your work here is very much appreciated! :D

Yah, pegging the XCode Cloud XCode version to 15.4 and our testflight builds work again on iOS 17.6.1