I don't see any certificates or CAs in the Passwords application, so now what?

My application suddenly started crashing on launch when I target "My Mac - designed for iPad." But only after the first build from scratch, which runs once. All subsequent runs crash with: dyld[90869]: Symbol not found: _OBJC_CLASS_$_AVPlayerView Referenced from: <D566512D-CAB4-3EA6-9B87-DBD15C6E71B3> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Debugger/libViewDebuggerSupport.dylib Expected in: <4C34313C-03AD-32EB-8722-8A77C64AB959> /System/iOSSupport/System/Library/Frameworks/AVKit.framework/Versions/A/AVKit I don't use AVPlayerView anywhere in my application. A file-contents search of the entire source tree doesn't turn it up either. The application doesn't even get to the point of instantiating the app object, so none of my code is involved. If I switch the target to my iPhone, it will build and run repeatedly. If I then switch back to "My Mac," it will build and run once... and then crash every time. Further research shows that this only happens in Debug builds. This is a major issue right now because iOS 18 broke authentication certificates (thus HTTPS), so anyone writing or debugging an app that needs network functionality must use HTTP on localhost. In my case, I'm dead in the water because I can't debug on my local machine. Has anyone seen something like this before? I can find no reference to anything like it.

Hi all. I renewed my membership, got a confirmation E-mail, and followed the link in it to check the status. It says "enrollment complete." But if I log into the developer portal, it says "membership expired." There is no chat option for support, only a form for E-mail. The response time quoted is up to two days. Meanwhile, I can't implement some critical features in an app I'm building, because they require an active developer account. Not cool, Apple. Anybody else experience this?

I have a project that has been building fine up until recently, when I started seeing spurious errors flagged in the editor on lines that were correct... and when the build was reported as successful and the app ran. The lines were often flagged twice for the same "error," and selecting the suggested "fix" produced syntactically incorrect lines because Xcode replaced the wrong characters. Now the builds are actually failing, on correct lines and preprocessing failures (allegedly missing header files that have never been missing before, with no project changes). Also there's a lot of Could not read serialized diagnostics file: error("Invalid diagnostics signature") reported in the build output, although that's categorized as a warning. Cleaning and deleting DerivedData has no effect. I'm not using CocoaPods or Swift packages, which you see cited in a lot of reports about this. Has anyone found a workaround?