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 challenge 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 challenge when Prod or UAT are chosen however I get totally different error messages for each of the schemes.

When making an attempt 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 correct entitlement.)
Confirm that the Developer App certificates to your account is trusted in your system. Open Settings on the system and navigate to Normal -> VPN & Machine Administration, then choose your Developer App certificates to belief it.

However there is no such thing as a certificates within the Settings app to pick!

When operating “UAT” the message says:

Couldn't connect to pid : “1235”
Failure Cause: 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 doubtless 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 informed me.

What I attempted:

• Nearly each resolution I’ve discovered thus far on the web

• Cleansing challenge construct folder, derived knowledge and system help

• Reinstalling cocoapods used within the challenge

• Deleting the app from the iPhone

• On the lookout for the log within the Console.app however I couldn’t discover something different
  than what Xcode already informed 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)

• Similar 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 bought the identical errors.
Surprisingly the “Take a look at” scheme works as I stated beforehand however I can not give you any clarification as to why.

Settings for all schemes look principally the identical.