@eskimo. Thanks for the reply. "Modern versions of macOS do not use CRL checks". I currently have Monterey 12.5.1, so presumably that's not doing a CRL check? The problem actually manifests before even attempting to do any code signing - if I open the keychain and click on a dev cert it says its valid, then if I connect the VPN and then click on another cert and then back to the first then it says not valid. So presumably Xcode is not even entering the picture here at this point?

@eskimo "One of the goals of a deprecation like this is to flush out the valid use cases." Are you saying Apple deliberately mark stuff as deprecated to see what complains for what reasons they get about it?? Here's a use case - if there is an application that is intended to run only with a certain carrier (for example Verizon app their own apps, etc.) then CTCarrier can be used to check this and let the user know before the user has to bother logging or attempting to log onto a system.

@eskimo Hello, is there approximate pointers to when CTCarrier will become actively deprecated and start to return --/65535. Will there be an alternative available to CTCarrier for carriers when that happens?

You need at least 500GB to install/run Xcode????? That's totally one million percent not the case at all. Where on earth did you get that figure from?

@SeanConrad Did you ever find out what the number of allowed updates is?

Delete me

@O_G did you find a solution? I've getting the exact same error about libSwift_Concurrency

Hello, yes thats correct the filtering entitlement wasn't used in my profile (as I don't have it). Is there anything that can be done regarding this such that the notification service extension can still continue to filter but can also use the call extension?

Did you ever find out any more info about this?