I recently updated my organisation developer program so I can use it one more year, but now my apps seem to be impossible to install, I got this famous error :
app_name can't be installed at this time
I got this problem on the App Store and for Ad Hoc distribution as well.
My certificates and my provisioning profiles are fine.
Did someone have the same issue recently ?
What could it be ?
Thanks in advance for your answers !
I believe you may have changed your app build settings and are likely not building with the enterprise distribution profile. That error usually means you are building with a regular development provisioning profile and the device's UDID is not in the list.
Verify your app's build settings are set to build using the Enterprise Distribution Profile.
If you do not believe that to be the case, post the Console logs from the device during an install attempt to find the actual error.
I finally found where the problem came from and it is a bit stupid. Actually, someone in my team recently changed our certificate on the Apple member center but didn't add this certificate to our build server.
After adding the certificate to the build server, everything worked as expected.
We're working on the same project 2 persons. I don't understand why Apple forces the use of a "Development" profile, since develop isn't really supposed to be signed but whatevs. My issue is each time we compile on our machines, XCode invalidate existing provisioning profiles and create a "Managed" one.
Obviously this isn't XCode fault, but we failed to understand how it is supposed to work. Can we get an step by step on how to set up both development and production on more than 1 machine, using the "Managed by XCode" option, so we don't have to create a CSR each time? Thanks in advance
The short answer? Don't manage your provisioning profiles with XCode, I myself and countless others have the same issue and the only way I found around it was to manage them myself or using something like Sigh
I'm trying to debug my app on Xcode and I'm having the following error:
The identity used to sign the executable is no longer valid.
Please verify that your device’s clock is properly set, and that your signing certificate is not expired.
(0xE8008018).
Now I know there are many questions regarding this issue, and I have tried every possible way to solve it, what I have tried so far (didn't work):
Some suggested to restart Xcode.
Refreshing the account.
Deleting all the certificates from the keychain.
Revoking all the certificates from the member center.
Installing the certificates manually.
Checked my Devices clocks (obviously)
Removed Xcode (disparately) and re-installed it.
Checking my project Build config, and made sure that the developer account is selected.
Checked my account expiration date (it's renewed 5 days ago)
Checked if I have to accept some Conditions and Terms (none)
Disabled the devices I have in the Member profile
Tested on multiple iPhones (same result)
Checked out a git tag/branch which is stable (I thought the project might be corrupted also disparately)
My concern is that it might be a temporary issue from apple, or a bug in Xcode, although it was working hours ago on my iMac, when I switched to the MacBook Pro I had this issue (and I always do this with no problems at all).
Running:
OSX Yosemite 10.10.4 (14E46)
Xcode 6.4
Trying to remove and re-add your apple id, it works for me.
xcode: Preferences...
Accounts
Select your apple account
Remove that (-)
Add again your apple account (+)
Run yor app!
After hours of investigating, the shell script for signing the project was failing at some point, without reporting back to Xcode.
I noticed that in the DerivedData folder (found in /Users/yourUsername/Library/Developer/Xcode/DerivedData/) of Xcode there were two folders with the same name of my project ending with a different hash, for example:
ProjectName--dcakkvkdhqvxstehdiuzwbpsmdal
ProjectName--kurbctkdhqvxuytrwnczwbpsmdal
I closed Xcode, and made sure to delete both folders, somehow Xcode generated two different folders for the project at some point, restarting Xcode after the deletion of the folders fixed this.
I have experienced the same situation.
But it was cleared by deleting and downloading again the provisioning profiles on my mac.
The location of the provisioning profiles is:
/Users/yourUsername/Library/MobileDevice/Provisioning Profiles/
I had the same issue. What helped me:
Set Profile to a wrong one (other project)
Run project and received the popup with information that provision profile is wrong and proposal to Fix the issue
Press Fix the issue
Just login to your developer account and create new developer certificate or revoke older one an create new. It will resolve the issue.
A Solution that might help some People
Go to developer.apple.com
go to the identities/certificates page
then click on Provisioning Profiles If you found few invalid
profiles just edit them
Make sure you check your main profile.
Click generate and close.
Now in XCode, remove your profile Add it again.
You're good to go
This will happen if you changed your Primary Email
Delete files and folders from:
~/Library/MobileDevice/Provisioning Profiles/
~/Library/Developer/Xcode/DerivedData/
The only solution for this problem is to delete the folder from
~/Library/Developer/Xcode/DerivedData/YourAppName-
This way everything will get back to normal !
Cheers !
All of the answers helped a lot but in my case developer certificate got expired that's i was getting this error while building the app.
Keychain -> Login -> My Certificates
So just removed the certificate and created new one worked fine for me.
NONE of this worked for me
vomako 's answer at The identity used to sign the executable is no longer valid
DID work -
i.e.
"Solution within Xcode:
In Xcode, go to Preferences --> Accounts --> View Details
Press the refresh button in the lower left corner (called Download all in Xcode 7)"
end of his post
It's a little refresh symbol now (circling arrow)
Then click on the Request button
Hope this saves somebody some time
I have solved the same problem. Just from "https://developer.apple.com/account/ios/profile/production/create" re-created the new Provisioning Profiles. Then download and install the new Provisioning Profiles of (Development and Distribution).
i am developing an native ios application on mac os mavericks image on vmware, i am doing a training in a company. this application contain PushNotification service. i have download a video tutorial and i complete all the tasks as the video show. but in the end when i install the provisioning profile it show this warning message : "valid signing identity not found" . i have work on this issue many days.
i am new in ios developing, so day by day i read questions of developers that have this issue also and i've read the answers and try to fix it but no result.
can anyone help me and guide what to do. down i will notice what i've see and i feel that this could be the problem and i can't do anything:
- when i create the provisioning profile , they gave me numbers of certificates to chose, none of these certificates is the one that i create.
There are probably many reasons for this message and many more potential solutions.
I often see this error message display when building. Quitting and restarting Xcode usually resolves the issue for me.
Have you tried downloading the provisioning direct from apple site? Sometimes I have problems when I try to update directly from xcode.
I know this may seem similar to other questions on here but just here me out. I'm trying to submit an iOS app to the store for a client, but cannot get his Distribution profile to show up in Edit>Project> Code Signing menu. I have downloaded and installed it. The strange thing is that it appears in the "Organizer." I have cleaned the project repeatedly and deleted my distribution profile. I'm on the verge of reinstalling XCode and the iOS SDK and am hoping that there is a better and faster way to solve this problem.
Please advise.
Ok, I have solved this. I had to delete and reinstall XCode after deleting all my provisioning and distribution profiles form my system