ios – Xcode – “Couldn’t connect to pid” and “app can’t be put in as a result of it is integrity couldn’t be verified” errors

In our undertaking we have now 3 schemes: Prod, Take a look at and UAT (one other one for testing)

For final couple of days I have been unable to construct and run the undertaking when Prod or UAT are chosen however I get completely different error messages for each of the schemes.

When attempting to run “Prod” I am getting:

Failed to put in embedded profile for app.xxx : 0xe800801f (Tried to put in a Beta profile with out the right entitlement.)
Confirm that the Developer App certificates in your account is trusted in your machine. Open Settings on the machine and navigate to Basic -> VPN & System Administration, then choose your Developer App certificates to belief it.

However there isn’t a certificates within the Settings app to pick out!

When working “UAT” the message says:

Couldn't connect to pid : “1235”
Failure Purpose: connect failed (Not allowed to connect to course of.  Look within the console messages (Console.app), close to the debugserver entries, when the connect failed.  The subsystem that denied the connect permission will possible have logged an informative message about why it was denied.)

However I could not discover something within the Console.app apart from what Xcode already advised me.

What I attempted:

• Nearly each resolution I’ve discovered to date on the web

• Cleansing undertaking construct folder, derived information and machine help

• Reinstalling cocoapods used within the undertaking

• Deleting the app from the iPhone

• In search of the log within the Console.app however I couldn’t discover something different
  than what Xcode already advised me. There was no entry created by the
  debugserver course of

• Restarting each MacBook and iPhone gadgets

• Downgrading Xcode to fifteen.0.1 (the error began showing once I was
  on 15.1 and updating to fifteen.2 did not repair it)

• Eradicating all certificates
  from Keychain and including them once more (we use Fastlane for that)

• Identical for all provisioning profiles

• Eradicating Mac and VisionOS from supported vacation spot in order that solely iPhone
  is left

These errors began showing in a single day, I went again to one of many older branches that undoubtedly labored earlier than and I obtained the identical errors.
Unusually the “Take a look at” scheme works as I stated beforehand however I can not give you any rationalization as to why.

Settings for all schemes look principally the identical.