What system are you on, Mac or PC? In your Project Settings>iOS>are your certificates and provisons high-lighted green and do they say “valid?” Under Project Settings>Packaging: What are you packaging for; Development or Shipping? Make sure your Bundle Identifier matches what you have set up as an Apple Developer: you will need to sign into your Apple dev account to check this. Finally, if on a Mac, check your Certificates in your KeyChain Access window and be sure they are up to date. You may have to update your certificates and provisions.
Let me know if none of these resolve your issue; be sure to note what you tried and what you did not.
I had this issue and got past it after doing the following. Hopefully it will work for you as well.
On mac, my provisioning profiles were marked as valid, but builds failed immediately after starting claiming that the provision was not found. After some frustration I noticed that their naming was different than on PC. The names given on mac was a long string of letters, numbers and some dashes while the PC version had the project name instead. Renaming them to fit the PC scheme, [projectname].mobileprovision or Distro_[projectname].mobileprovision, and placing them in ~ [projectfolder]/Build/IOS, made them appear alongside the other profiles in the editor after restarting it. Picking the renamed provisioning profiles made it possible to get past the problem.
In short, rename your profile files to [projectname].mobileprovision or Distro_[projectname].mobileprovision, and place them in ~ [projectfolder]/Build/IOS, then pick them as they appear in the editor after a restart.
I’m thinking the issue could be a change in how the profiles are handled. I’m sure it worked in older versions of the editor to just get the profiles through xcode or download and run them, adding them to the key chain. It seems that now the editor still sees the profiles in the key chain and recognizes that they are valid, but fail to access them when the time comes to build.
Hi Steve, all i had to do is manually import the provision profiles using the ‘Import provision’ button and manually select to use the imported provision. Rather than mark the Question/problem as resolved with a workaround can you please log it as a bug to be fixed?
I have the exact same problem, but the workaround doesn’t fix it for me. Both the original provision and the renamed one (via the workaround) show up and say valid. Selecting either one makes no difference, I get the “Provision not found…” and “Signing key not found…” errors instantly.
Let me clear up why those fail now. In Xcode 8, those are considered Managed Provisions and can not be used in the new manual signing mode, so they are being ignored during the detection of provisions during the final code sign pass by our system. The work around is as suspected to rename them or import the provision utilizing the editor. I’m working on a way to utilize them, but as they currently stand, they can’t be used in a manual sign and the current thought is to detect it as valid and then make a copy of the file without the id as the file name.