The identity used to sign the executable is no longer valid

IosXcodeIpadXcode4

Ios Problem Overview


I have an application that I am debugging on iPad. 2 days ago I wanted to debug a same updated application but I am having this 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).

I don't have iPhone Developer certificate yet, but I have debugged this game once.

Ios Solutions


Solution 1 - Ios

Neither restarting Xcode nor restarting my Mac helped.

Solution within Xcode:

  1. In Xcode, go to Preferences --> Accounts --> View Details
  2. Press the + symbol and select iOS Development
  3. Press the refresh button in the lower left corner (called Download all in Xcode 7)

PS:

  • Sometimes it may also help to delete invalid provisioning profiles: right-click -> move to trash
  • I saw this error exactly one year after signing up as an Apple developer.

Solution 2 - Ios

Try restarting XCode. It worked for me.

Solution 3 - Ios

This may happen when your certificate expire in your Key Chain.

EDIT : I'd now recommand cert and sigh to generate your certificates and provisionning profiles. These are two commands part of the fastlane tools from KrauseFx.

Using cert & sigh:

  1. Open a terminal and type cert
  2. Answer the prompted questions to sect your user, password, team, app, etc.
  3. Open a terminal and type sigh
  4. Answer the prompted questions to sect your user, password, team, app, etc.
  5. Select the right profile in Code Signing Identity (iPhone Developer)

Conventional way:

  1. Just go to the new provisioning portal : Certificates, Identifier, Profiles
  2. Login with your developer account.
  3. Go to Certificates and click the Plus button.
  4. Then select iOS Apps Development and click Continue.
  5. Follow the whole process and download the newly generated certificate.
  6. Download it and put it in your keychain.
  7. Update your profiles from XCode Organizer devices window
  8. Select the right profile in Code Signing Identity (iPhone Developer)

Solution 4 - Ios

If all the above previous suggestions fail after renewing your certificate, as they did for me, browse to the following location;

~/Library/MobileDevice/Provisioning Profiles

...and delete your provisioning profiles.

Then download your provisioning profile again from;

https://developer.apple.com/account/ios/profile/profileList.action

Solution 5 - Ios

If you are using jailcoder, make sure you jailbreak your iphone successfully. Don't forget install AppSync for IOS in Cydia.

Solution 6 - Ios

In the latest update from xcode this problem usually occurs when your certificate has expired and xcode continues to use the old one until it has expired.

Closing xcode and opening it again will fire off an automatic process of downloading your new certificate and getting your app working.

Just close xcode right down (Cmd + Q) then open it back up again, load your project and hit play .. it will ask you if you'd like assistance to auto fix the certificate problem then you just follow the onscreen instructions and it does all the hard work for you :)

Solution 7 - Ios

You have your provisioning profiles outdated.

  1. xcode
  2. Preferences
  3. Accounts
  4. Select your apple id
  5. View Details (Right-bottom corner)
  6. Download All
  7. Run again and DONE!

Solution 8 - Ios

This may be somewhat of an empirical approach but is worthwhile in the face of many commentators noting either "this worked for me" or "this didn't work for me". Firstly, the problem can lie in a number of locations, either your certificates (code signing identities) or your provisioning profiles. Identifying where the problem lies first before doing anything will save a lot of wasted effort. You will need to check in three places:

  1. XCode
  2. Keychain Access
  3. The Developer Portal (Developer Members Centre)

OK, in XCode click on the Project (Above the Targets Heading), select Build Settings and scroll to 'Code Signing'. Expand the 'CODE_SIGNING_IDENTITY' heading and you will see a bunch of identities (Debug, Release etc.) Each one of these will match up with a certificate in Keychain Access. Find the match and check the expiry date...if it has expired you will need to update it in the Developer Portal and download it. Check EVERY identity, not just the first one you find that has expired. Also, if it has expired you will need to regenerate any provisioning profile that used the expired certificate. If no problems with the certificates, check the expiry date of all the Provisioning Profiles. Once again, if they have expired, they will need to be regenerated.

Once complete, repeat the same process for the TARGET you are trying to build for.

None of this worked? An expired certificate is lurking in one of your provisioning profiles. A sign that this might be the case is that when you click on a CODE_SIGNING_IDENTITY the identity is below Other... eg.xcode example of dodgy identity

This is usually a sure sign that there is an expired certificate lurking about and that one of your profiles is using it.

Solution 9 - Ios

I faced to this problem when my membership was expired and I renewed it. I use xCode6 and I solve this problem by revoking expired developer certificate from Member Center and cleaning build folder ( alt+[Product>Clean] ). xCode handle others issue itself.

See "Replacing Expired Certificates" section on this link: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html

Solution 10 - Ios

I had this problem with XCode 6.3 Below is the steps that worked for me.

Go to XCode > Preferences > Accounts Select your developer account then click View Details... Click on the refresh button on the left bottom of the window. It should notify you that you're missing few certificates. Click Request. XCode automatically should download missing certificates. Click Done and it should work.

Solution 11 - Ios

you debug it on simulator only if you don't have iPhone Developer certificate. check on left corner in xcode you select simulator not device.

Solution 12 - Ios

I faced the same issue, I deleted all provisioning assets from xcode & added them back, and just relaunched Xcode.

My App was loaded on to the device and it worked.

Solution 13 - Ios

This does also happen if your developer certificate is expired. Time to pay apple and renew it :P

Solution 14 - Ios

First: go to build settings and check, if your valid Code Signing Identity is chosen. If that doesn't help, try the more complicated stuff

Solution 15 - Ios

In my case, this dialog message worked

> 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).

My certificate in Keychain Access was given status to be not valid yet in red color with expiry about one year and an hour in future. I set my time to be one hour ahead and status of the certificate became valid in green color. So, anyone out here who thinks the solution to be the xcode restart is not correct but it would be cause of time elapsed of the xcode restart to make the certificate valid. As, by clicking the Fix Issue button revokes and creates new certificate with exactly one year ahead (plus some minutes depending upon locales to raise this issue).

Solution 16 - Ios

This answer is exactly work for me .


146 down vote Neither restarting Xcode nor restarting my Mac helped.

Solution within Xcode:

In Xcode, go to Preferences --> Accounts --> View Details
Press the + symbol and select iOS Development
Press the refresh button in the lower left corner (called Download all in Xcode 7)

PS:

Sometimes it may also help to delete invalid provisioning profiles: right-click -> move to trash
I saw this error exactly one year after signing up as an Apple developer.

*** What I want to know is why this problem occur frequently after November 。 ps:My Apple Developer Account has been signing up several years.But this year I have changed Agent role to another e-mail account.

Solution 17 - Ios

My solution, after nothing else worked, was to go to Keychain Access and delete all "iOS developer" keys/certificates, then let Xcode regenerate them.

Solution 18 - Ios

Try setting the time on the mobile device and the Mac to "set date and time automatically" checkbox and restart xcode, that did it for me

Solution 19 - Ios

The Problem here is that your profile was built on an expired certificated

-so you have to go inside the developer portal and renew your certificate if it was expired

-then regenerate the profile so it will be rebulit on the new certificate

i suggest to use the iPhone configuration utility tool to manage profiles on your mac

Solution 20 - Ios

If your certificate is not installed locally. Or you tried running the certificate and opted to "revoke and request" a new certificate then you have the option to do that on the machine you are trying to run on

go to Preferences-> Accounts-> under your AppleId -> View Details -> under signing identities you can see the status of your certificate "Valid" or "Revoked" if revoked and you want to request a new one go to the -> + then -> the type of distribution you are trying to use.

Solution 21 - Ios

In Xcode 5.1 - there is a self help area that did the job for me.

You'll find it in the General section after clicking on your project name under > Targets. You should see a warning icon and a description of the issue in the Identity section (right where you type in your build/version numbers).

It noticed that there was no certificate currently stored and via some self-help boxes and a change of my password, I got it going.

Solution 22 - Ios

These were the reasons I had this error:

The App ID didn't have my iOS Developer Certificate checked (I'm a member of an Enterprise program) and I had 2 provisioning profiles with the same App ID in my Mac. I deleted one.

Hopefully this helps someone.

Solution 23 - Ios

I had this problem several times, normally it can be solved by close-reopen Xcode.

I did delete derived data from Xcode organizer. It eventually works

Solution 24 - Ios

I tried all of the above. I kept getting the error about the UUID not being found.

I went to the project, opened project.pbxproj and found all instances of the UUID (2) and deleted the UUID (not the entire line).

Fixed the problem.

Solution 25 - Ios

I fixed this issue by selecting the correct team within Xcode (I'm part of multiple teams). Also, I revoked my certificate, requested a new one, uploaded that, and then re-downloaded it.

Solution 26 - Ios

Experienced the same issue. Was an issue with an expired certificate. You'll need to create a new cert and corresponding prov profile. Follow dulgan's advice for doing so.

Solution 27 - Ios

Removed the profiles from the directory on your machine: "~/Library/MobileDevice/Provisioning Profiles". And logged to apple developer centre and edited the specific provisioning profile and selected the certificate for provisioning profile and generated the profile again. Installed the new profile and it worked for me.

Solution 28 - Ios

Found another way this occurs today. When you edit your provisioning profile after a certificate change you can see the certificates selected says 2 of 1 certificates selected (if you just use 1 certificate). Just by unselecting and reselecting the certificate you can regenerate and install the profile and it solves the problem.

Solution 29 - Ios

@vomako 's solution almost solved my problem but I had to take another couple of steps.

I refer to the following...

> In Xcode 6.1.1, I went to Preferences --> Accounts --> View Details

After upgrading to Xcode 6.1.1, the main issue for me that the >View Details button was greyed out.

I had to delete my account, restart Xcode, then add my developer account back in.

After this step, I could yet again view details and refresh my provisioning profiles.

Solution 30 - Ios

I selected None from Team dropdown in target general settings. Then selected the original team. Xcode shows some spinner next to it. Wait for it to complete and then everything works. Tried it in Xcode 6.2

Solution 31 - Ios

Today I faced this issue on my Xcode 6.3 public release.

I tried to restart Xcode several times but issue remained there.

What worked for me is

Manually create a new development profile at "http://developer.apple.com" 
download and install this new profile, select this new profile from xcode build and run.

Solution 32 - Ios

Same happened to me, In my case I just needed to approve apple's ne terms of service over: https://developer.apple.com/membercenter

Solution 33 - Ios

I took a bit of a hiatus from iOS to work on an Angular project and had this surprise waiting for me when I came back :-) In my case, I think it had to do with the fact that Apple is merging its developer programs, (at least from what I understand they are merging their developer programs), and I had to accept their new agreements.

Anyways, to fix this I combined a lot of the answers you'll find here and scattered throughout the web.

First, make sure to accept any pending agreements through both iTunes Connect and Apple's developer center. Make sure to accept any agreements in the "Agreements, Tax and Banking" section in iTunes Connect.

Second, via Xcode, go to Preferences -> Accounts -> View Details and at the bottom left there should be an option to refresh your profiles. When I did this Xcode installed a few new profiles.

Finally, restart Xcode.

Give some time in between each step for Apple's servers to update if these steps don't work right away.

Solution 34 - Ios

I solve this problem using the new provision profile from apple developer account, Clean Derive-Data, And Refresh Developer Account in XCode.

Thanks your support. :)

Solution 35 - Ios

I came through this error. The problem was The developer identity and Mobile Provisioning Profile mismatch.

Delete keychain certificates and fresh install matching provisioning profile and developer certificate fixed the problem.

Solution 36 - Ios

I have tried many method to solve this problem.But they did not work. Including

  • restart my Xcode or my Mac.
  • delete invalid profiles and generate again.
  • reset Xcode > Preferences > Accounts.
  • update iOS version and Xcode version.

What finally worked for me is:

> register a new apple developer account and add to Xcode

I think maybe my developer account has some problem.

Solution 37 - Ios

I've resolved editing my provisioning. In fact, i've noticed that this mobile provisioning was not associated with my signing identity.

So, from the developer apple i followed this step: Select Provisioning Profiles -> Edit -> check my identity from "Certificates".

Effectively it's a strange error...

Solution 38 - Ios

I had this problem and tried everything here but it didn't help. Then I noticed that the cord I was using was a little frayed, so I tried a new cord and it worked.

Solution 39 - Ios

I have one strange problem. In fact when i plug my phone to my mac the time of the device change but not use the actual hour. For example on my computer I have this hour : 05:17 pm but on my phone when is unlocked time is frozen to 09:41 am so when i try to build my app on phone from xCode i have the next error message :

Please verify that your device’s clock is properly set

The strange thing is that when my phone is still pluged to the mac the time on lockScreen is good (05:17 pm)... And if i check on Date & Time on general settings I have this strange thing too (time of statusbar is wrong but time below is good) :

Wrong time on statusBar

After few minutes i understood that it was because of QuickTime Player which was running on my mac with view of my iPhone (i was going to save a video demo of my app).

To resolve the problem I had to quit all applications and restart computer.

In plus at the end if problem persists do these steps :

  • xcode: Preferences > Accounts
  • Select your apple account
  • Remove it
  • Add your Apple account (+)
  • Run your app again.

Hope this can help.

Thank you,

Solution 40 - Ios

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).

enter image description here

Solution 41 - Ios

Method no 12454: Set invalid (or any other) provisioning profile -> compile (you get error). Then set the correct provisioning profile. Might as well work ( did for me )...

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionHayk MelkonyanView Question on Stackoverflow
Solution 1 - IosvomakoView Answer on Stackoverflow
Solution 2 - IosNamrathaView Answer on Stackoverflow
Solution 3 - IosdulganView Answer on Stackoverflow
Solution 4 - IosAnthonyBlakeView Answer on Stackoverflow
Solution 5 - IosAndrewView Answer on Stackoverflow
Solution 6 - IosKevin SView Answer on Stackoverflow
Solution 7 - IosSebastián LaraView Answer on Stackoverflow
Solution 8 - Iosarcady bobView Answer on Stackoverflow
Solution 9 - IosCoyBitView Answer on Stackoverflow
Solution 10 - Iosu54rView Answer on Stackoverflow
Solution 11 - IospriyankaView Answer on Stackoverflow
Solution 12 - IosJyothi SwaroopView Answer on Stackoverflow
Solution 13 - IosRaj Pawan GumdalView Answer on Stackoverflow
Solution 14 - IosbrainrayView Answer on Stackoverflow
Solution 15 - IoszeeawanView Answer on Stackoverflow
Solution 16 - IosmagicyaView Answer on Stackoverflow
Solution 17 - IosmaniekView Answer on Stackoverflow
Solution 18 - IosWaqlehView Answer on Stackoverflow
Solution 19 - IosOmar FreewanView Answer on Stackoverflow
Solution 20 - IosDaisy R.View Answer on Stackoverflow
Solution 21 - IosChris LambrouView Answer on Stackoverflow
Solution 22 - Iosuser3900346View Answer on Stackoverflow
Solution 23 - Iosr0n9View Answer on Stackoverflow
Solution 24 - IosDorrinView Answer on Stackoverflow
Solution 25 - IosViperView Answer on Stackoverflow
Solution 26 - IosJoshua BookView Answer on Stackoverflow
Solution 27 - IosMinnaView Answer on Stackoverflow
Solution 28 - IosAdbCView Answer on Stackoverflow
Solution 29 - IosandrewbuilderView Answer on Stackoverflow
Solution 30 - IosJeetView Answer on Stackoverflow
Solution 31 - IosIrfan DANISHView Answer on Stackoverflow
Solution 32 - IosDanielZivView Answer on Stackoverflow
Solution 33 - IosMichael EView Answer on Stackoverflow
Solution 34 - IosIlesh PView Answer on Stackoverflow
Solution 35 - IosAlvin GeorgeView Answer on Stackoverflow
Solution 36 - IosHongyue SunView Answer on Stackoverflow
Solution 37 - IosAlessio CampanelliView Answer on Stackoverflow
Solution 38 - IosTom KincaidView Answer on Stackoverflow
Solution 39 - IosO. BoujaouaneView Answer on Stackoverflow
Solution 40 - IosylgwhyhView Answer on Stackoverflow
Solution 41 - IosPawel KlapuchView Answer on Stackoverflow