Error "A valid provisioning profile for this executable was not found" in Xcode 10

Weird that suddenly I get "A valid provisioning profile for this executable was not found" in Xcode 10. Though the build is successful it fails to run on physical devices. Does anyone face the same problem after updating Xcode to v10?


I have valid Enterprise licence for App development.


Issue:

1. Update installed in Xcode late night yesterday

2. Created archieve file (IPA) using distribution profile & certificates

3. No issue in IPA installation & usage

4. Tried to change the signing to developers profile for debugging

5. Build successful

6. When tried to run on physical testing device, I get installation error "A valid provisioning profile for this executable was not found"


Steps tried:

  1. My testing device available in the team
  2. Recreated all the certificates
  3. Recreated profiles
  4. Installed cerificates, profiles on my mac
  5. Cleared all the provision profiles from my testing device & installed the new one
  6. Clean build successfully
  7. Run failed with message "A valid provisioning profile for this executable was not found"


Solution Found:

1. To change Build System "Legacy Build System" under workspace settings

2. This change worked and I was able to run the app on my testing devices


My Question:

Why should I change build system if "New Build System" was successful before the update?

Replies

Thanks @ayyanar7, that solved the exact issue on my end as well.

Thank you @ayyanar7... it's works for me..


really you done a great job.. cheers!!

Hi,

In my case, I don't have project in my workspace in local XCODE. I am getting a .xcarchive (converting to .ipa file) from third party for an Hybrid app. How should I resolve this issue?

simlar sittuation for me. Did you find a resolution?

I got this error when installing the debug build on my physical device.
I thought it was because of updating XCode from 11.4 to 11.5, but that was not the reason.

In my schema definition it was set to "Release".
Goto Products > Schema > Edit Schema > Change to "Debug"

That resolved the issue
Just go Signing and Capabilities,
check "automatically manage signing",
finally click on Register device, this will create the provisonning profile on your device

That resolved the issue