Same problem here, but it doesn't seem to involve a third-party lib. In a project that has been building fine for years (and as of a few days ago), suddenly I'm getting the reported error. After that the compiler flags some lines for "Value of type X has no member Y," but it's bogus because X certainly does contain Y. I don't use CocoaPods or any other third-party shenanigans. Thus far no solution.

I tried "all runtime issues" in Xcode 13.2.1 and it doesn't work on failed assertions.

"All runtime issues" exists in Xcode 13, but doesn't work for failed assertions.

Apple inexplicably doesn't capture logs for anything before iOS 13, even though the function has been around for years. Oh wait... that's in TestFlight. For released apps, there are no crash reports anywhere in the portal that I can find. Which means that if they're there, they may as well not be.

I have certificates on my computer for my Apple developer account. I verified one for code signing with Keychain Access, and signed the PHP lib with it. But when Apache tries to load it, it still complains "No code signing authority." But the certificate shows "Apple Worldwide Developer Relations Certification Authority". WTH? Then I created a new certificate authority, during which it asked which certificate I wanted to use (why?). I picked my Apple Developer one and re-signed the lib. Nope.

Thanks a lot for your reply!

The problem with the app is that it automatically captures a sysdiagnose and system report when you start a new report, which is dumb and means that erroneous or irrelevant files end up attached to your report. Even better is that there's no way to delete them if you submit the report before noticing that they were added without your permission.

Except that it does so without permission, thus often captures irrelevant or wrong information. For example, one of my computers had no Internet access, so I had to file a report on another one. So of course Feedback Assistant attached diagnostics from the wrong computer behind my back, and there's no way to disable this behavior.

Pretty pathetic that we need this, but I'm using it with a .6 delay and it works. Thanks man. I can't resist mocking the fact that a UI toolkit went out the door with no way to set initial focus... and remained that way for years.

Unbelievable.

Thanks for the reply. I looked at the options, but under "Info.plist values" there's no way to add any. So the question remains: Will adding key/value pairs to the app's .entitlements file propagate them into Info.plist if necessary?

Thanks, but still not seeing any way to add values in the UI. Ugh, see below.

Thanks. That screen shot is odd, because it shows "Build Settings" selected, not Info. I don't have anything like those entries in my build settings. On the Info page... that is some absymal UI. I mean... not only are the + controls invisible unless you happen to roll over them, but they are depicted as only applying to one setting... not as if they add entirely new entries to the overall list. Unbelievable. Thanks! I did add the options I'll need. But the simulator doesn't prompt for them...

But what if the optional is nil?

Thanks, but that's essentially the same "solution" I posted. It still requires that I implement this nonsense for every member of every class I want to expose in a UI. Totally impractical.