iOS Development

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

Spread the love

In our mission now we have 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 mission when Prod or UAT are chosen however I get completely 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 : 0xe800801f (Tried to put in a Beta profile with out the correct 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 & Gadget Administration, then choose your Developer App certificates to belief it.

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

When working “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 (, 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 aside from what Xcode already instructed me.

What I attempted:

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

  • Cleansing mission construct folder, derived knowledge and machine help

  • Reinstalling cocoapods used within the mission

  • Deleting the app from the iPhone

  • On the lookout for the log within the however I couldn’t discover something different
    than what Xcode already instructed 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 acquired the identical errors.
Unusually the “Take a look at” scheme works as I mentioned beforehand however I can’t provide you with any clarification as to why.

Settings for all schemes look mainly the identical.

Leave a Reply

Your email address will not be published. Required fields are marked *