Since upgrading to xcode 6 yesterday i have problems running an app from xcode on one of my devices and i have no idea why.
The message is:
A valid provisioning profile for this executable was not found
I have checked all the solutions from A valid provisioning profile for this executable was not found and "A valid provisioning profile for this executable was not found" error when trying to run unit tests but everything is correct.
So i have the right provisioning profile set, it is installed in the list of provisioning profiles on the device (and not expired) and the build configuration is debug.
I have no further ideas now.
EDIT: another device has no problem. So it might be specific to iphone 6.
As your profile is working on one device that means issue is related to your iPhone 6 device.
You can try the following steps :
1) When you create your provision profile, check whether your device is selected for that particular device. If not then select and again download the provision profile and install it.
2) Just see in your phone whether you have any expired provision profiles. If yes then delete all expired provision profile first.
3) Delete your application from your device if it is previously installed.
4) Select proper provision profile in your project and hit run.
Try following steps:
Open Build Settings > Select Code Signing
Provisioning Profile > Automatic.
This is work for me. :)
Related
I'm getting the following error message from Xcode 9 GM when trying to do an Ad Hoc distribution export of an iOS app archive from the Organizer.
Profile doesn't match the entitlement file's value for the
application-identifier entitlement.
The bundle identifier and the App ID do match. I never got this message for the same project with Xcode 8. So where is the new mismatch? Something I need to do in Xcode? Or is there some new setting when creating an App ID or Ad Hoc distribution provisioning profile in iTunes Connect?
The mismatch is in the provisioning profile being used. I can't tell you why, but the entitlements are being extracted from your provisioning profile during signing, based on the portal appID that profile was created from. There's a mismatch between the bundle ID of the target you built and the bundle ID of the portal's appID record that the signing provisioning profile was created with.
First, make sure that the profile is the one you're meaning to use (the AdHoc Distribution provProf for a portal appID that matches the bundle ID of your target, and if that looks right, consider regenerating the AdHoc provisioning profile and installing it using the Xcode>Preferences >Accounts "Download Manual Profiles" option.
Sometimes Xcode will get confused if you have old versions of provisioning profiles installed, and I've even seen times in the past where a wild card profile was matching instead of the intended one. So, there could be some Xcode confusion around the installed provProfs. The fact that you had no issues with Xcode 8 but do with Xcode 9 might explain that. Changes in Xcode can cause changes in behavior.
If regenerating the provProf and installing it doesn't help, I'd suggest deleting all of your installed mobile provProfs and then reinstalling them. To delete them, open a terminal window and enter
rm ~/Library/MobileDevice/"Provisioning Profiles"/*.mobileprovision
Then go back to the Xcode>Preferences>Accounts and do the "Download Manual Profiles" option to install them again. If it still doesn't work, you're missing something. See the debugging tip below.
Focus on the appID's bundle ID in the Dev portal, the bundle ID of your target, and the provisioning profile you're signing with (making sure it's for an AdHoc build of that appID). At least one of those isn't matching up.
One last debugging tip. Drag the provisioning profile you're signing with to TextEdit (I keep that in my dock for pretty much this reason.) TextEdit will display the information in the provProf, so you can check the entitlements and make sure they match what you're expecting.
Hopefully that's enough to sort this out.
Same issue appeared to me with both Jenkins and my local machine.
Not sure how it got fixed, but below one did the trick.
1: Navigated to build flavour in Target > General
2: Changed the provisioning profile to something else in that build flavour and archived.
3: Then selected back the actual provisioning profile. It worked like a charm.
Might not help in your case, but it worked for me.
I have already searched and almost implemented max solution but it's not installing any app even though if I am creating just sample single view app.
App installation failed
A valid provisioning profile for this executable was not found.
============== update ====================
I fixed this issue today.
First, go to ~/Library/MobileDevice/Provisioning Profiles.
Make sure Xcode isn't running.
Then, delete all provisioning files (like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision).
Start Xcode.
You will see something like "Fix this issue" in your Target's General tab.
Click it.
Xcode will now load new provisioning profile.
That's it.
----------- OLD Answer -------------
I have same problem now.
I've checked my provisioning profile using https://github.com/chockenberry/Provisioning/releases.
In my case, my provisioning profile had the wrong UDIDs but right machine count.
I've registered machines, and Apple Developer Center listed right UDIDs for those machines.
However, whenever I downloaded new provisioning profile, it contained wrong UDIDs.
I think Apple's system is outputting wrong provisioning profile.
I called Apple support for this issue today, but Apple only emailed me with their knowledge base links(forums,documents,etc).
Possibly you are using App Store distribution provisioning profile. Use development or Ad-Hoc provisioning profile.
For Xcode 8 / Swift 3.0
In my case, for my app target and my extension in "General" I check "Automatically manage signing" and it work
I was having this issue because the date/time on my iPhone was not the same as that on my Mac running Xcode ( i changed the date on my iPhone while testing some app).
On my iPhone, i went to Settings > General > Date & Time > Set Automatically
This fixed it
Make sure you have added device UDID in your provisioning profile.
Go to provisioning portal.
Edit provisioning profile.
Make sure device is checked.
Done, download
Use new Profile
Another possible reason: Device date is set to later than the expiry of you provisioning profile.This is very weird but, it could happen.
In my case it was that the running option in the building scheme was set to Release so it was trying to sign it using the appstore provisional profile not the development or the adhoc one. I had to set it to Debug to fix this!
I could run on Simulator just fine, but trying to install the App on device was throwing this exact error.
I had a test target in addition to the main target. The test target had signing set to a different team and profile. Setting the unit test target to match the main target settings for signing solved my issue.
Didn't notice it had been automatically changed over to a different team, was caused by being added to a new Enterprise team.
In my case, I went to the Apple Developer website and added the phone to the Provisioning Profile.
Then I re-downloaded the Provisioning Profile and worked =)
In my case was The build system. I had to change the default build system in "File > Project / Workspace Settings" and change it to the Legacy Build system.
For me, it's because the project I was trying to build is someone else's. The bundle identifier does not match with my team's provisioning profile.
Change bundle identifier to something else help.
In my case, my certificate is overdue..
The following worked for me:
Install the app using Personal provision profile (re-install after going into your phone settings and trusting the profile)
Delete the app from ypur phone
Switch back to registered developer profile and try again
In my case iOS 14.4, rebooting the iPhone solved it.
I can't get Titanium to accept my provisioning profile.
I am using Titanium to build a development app to run on my iPhone and that of two others. I have created the certificates, app ids, and provisioning profiles but when I come to create a package for distributing via iTune I get the error:
"Specified Provisioning Profile is invalid or is the wrong type"
I have tried pretty much every option I can think with respect to ways to build the package and types of provisioning profiles but it consistently fails with this message.
Is there a solution to this problem?
I always get xCode to build correctly first. I set up a blank helloWorld application in xCode and follow the Apple guide there on their resources site. Once this is set up titanium will pick up on your valid certificate and provisioning profiles.
Check that when you are trying to run the project you have removed any invalid or old provisioning profiles. This can be done under xCode device manager > Selected device , click the settings wheel in the bottom left > Show provisioning profiles... You'll then see a list of profiles you re trying to build with, if you've created a couple that have the same name it could be selecting the wrong one.
I am using Xcode 4.6.3.
I am getting this error messages while running the application in iPad,But first it was running correctly. Now we have renewed our license so i have changed certificate and
profile.still the same error appears
Please help me...
you need to follow this step:-
You Provisioning profile Generate with developer certificate from iTunes dev center.
remove old install App from device may be you Ipad contain old profile reference.
After connect your device to Xcode-Organizer->device->yuorIpad->Provisioning--check there old Provisioning profile is ther or not. if there then remove it.
In your target And Project check-> your Identifier is currect or not for example com.yourprofile.yourId
In Build setting you->code signing ->selection profile is correct identifier or not
Now just clean your Project. Build and run.
EDIT
Do not forget to Adding New testing Device ID into your new Generate Provisioning profile. in iTunes Dev there is Column to adding Device and also asking Device while you Generate Provisioning profile. May be you forget this step.
be sure that you are generating provisioning profile after adding device, or when you're just renewing profile.
And your provisioning profile must be linked with certificate, that you have in keychain.
(certificate+key)
All devices must be readded on demand, after renewing dev program (!)
In general, It's pretty sraightforward (just try it from the clean sheet, delete all the old stuff)
1) cert signing request
2) appid (if new app, if old just skip, optional - apns stuff)
3) certificates dev/distr (import them)
4) devices
5) provisioning profiles (import them)
in xcode choose in all positions needed profile, sometimes choosing parent option do not change profile for all fields of "Signing Identity" in xcode.
Deleting of old provisioning profiles is optional, it's not a problem when you have many of them
it's only problem when signing identities are more then one, ie: old expired and new one.
(In xcode 5 it will be easier to choose identity)
EDIT: it really seems like in build settings in code signing identity select options (some option) an old profile is chosen, and xcode gives this error.
I get this message when I start a build to my device in Xcode;
Code Sign error: A valid provisioning profile matching the application's Identifier 'vindfyrar2' could not be found
I've been through all the certificate/provisioning profile verification process.
I have valid provisionings profiles installed on my device in xcode organizer.
What I think is my problem is that I can't see any provisioning profiles in the target or project build settings -> code signing identity.
Take a look at the pictures below please!
Anyone please have some time to help me?
Whenever I encounter this problem, I find that restarting Xcode and selecting a different provisioning profile in your project (not target) build settings will cause the list to refresh. If you see no profiles anywhere, download them again from your apple developer center and drag them into the Organizer's Provisioning Profiles pane.
In the project build settings, set the Code Signing Identity to Automatic Profile Selector (iPhone Developer). Now check that Code Signing menu again, it should say "(currently matches: iPhone Developer: Jan Gifvars (xxxx) in 'iOS Team Provisioning Profile:*)". If it doesn't, you need to make sure you've got proper private key, certificate, and provisioning profiles. Follow ALL the steps in this tech note.
https://developer.apple.com/legacy/library/technotes/tn2250/_index.html