Codesigning error

[joedee]

I'm getting the following error when trying to run the app signer:

Codesigning error

You appear to have a error with your codesigning certificate, do you want me to try and fix the problem?

I'm running El Capitan and XCode 7.3 with a free Apple Developer account. Version 1.8 of iOS App Signer.

Tried running the fix option but not effective.

[DanTheMan827]

If you go into keychain and then view your signing certificate does it have any error by it?

[joedee]

No it looks good.

Probably connected; I do get an error when I try to add a new App Group in XCode:

And when I try to run the project in XCode:

[DanTheMan827]

The blue circle with the plus in keychain means that the certificate was manually trusted

Open the properties for your certificate and change the Trust type from "Always trust" to the system default

That should fix the signing certificate issue

Although, it seems like you may have other certificate issues than just the signing certificate... Is your system clock correct?

[joedee]

Ya I'd manually changed to see if that would change anything. I set back to System Defaults and same result. System clock is set automatically, so yes that should be fine.

[DanTheMan827]

And after it was set back to System Defaults it didn't report an error in keychain at all?

What you can try is to delete the account from Xcode, then go into Keychain and delete the certificate.

Then when you sign back in to Xcode it will ask you if you want to reset the signing certificate.

You will have to re-sign any apps you may have successfully signed before (if any)

Also, if you do that the existing provisioning profiles will no longer be valid... those can be found at ~/Library/MobileDevice/Provisioning Profiles (you can use Command+SHIFT+G in Finder to easily go there)

Just delete the files in that folder (Xcode will re-download them as needed)

[joedee]

Tried this too but no luck.

Worth noting that in version 1.7 I get the "Error processing deb file" and in version 1.8 I get the codesigning error.

[owen161]

Im using 1.8, follow all the steps through x-code to obtain the certificate and provisioning profiles and the application runs with no errors, however when I attempt to install the app through the devices method it fails with the message, App Installation Failed, The application does not have a valid signature. It is the same response I get if I hadn't used your IOS App signer software. Appreciate your thoughts.

[Furnan]

Hi,

Same issue here.

I'm running El Capitan with a free Apple Developer account. Version 1.8 of iOS App Signer.

Tried running the fix option but not effective.

[Sn0wCooder]

Same problem

[Sn0wCooder]

Plz help me

[adriannabarro]

Hello

I'm having this issue on macOS Sierra. Happy to contribute however I can.

[adriannabarro]

Hello again.

I'm still seeing this using the latest version (1.8.2).

[Beachiie]

Hi there, I also experience the same problem with OS Sierra and the iOS App Signer 1.8.2

Please advise..

[LisbethC]

I found this on the internet and I worked:

This was caused by a certificate that expired, You have to delete the expired certificate from keychain before you install the new one.

[xjrcode]

Same here with no expired certificates...

[True-Design]

Im getting the same issue aswell. I have tried everything you mentioned but no luck. Any suggestions?

[maclamont]

I have the same issue. Deleting the certificate and changing the trust settings doesn't do anything

[kmddd59]

SecKey API returned: -67808, (null)/var/folders/gm/nwvzn56j3t1cchmltp0t5p380000gn/T/com.DanTheMan827.AppSigner.CPPhiLOk/out/Payload/FreeDyn.app: invalid signature (code or signature have been modified) In architecture: armv7

i have attached the files below I'm using all latest stuff and i get that error above this is the first time i have seen this so i don't know what is happening here

Archive.zip

[adriannabarro]

Sad to report this issue is still in in 1.8.3.

[kmddd59]

@DanTheMan827 I'm contacting u here because i can't seem to find any other way id like to see if there is a way to allow resining iOS apps that use apple watch apps to work it seems to me every time I'm on the resigner it won't send the watch app through even if i use iTunes and I'm jailbroken so i thought maybe thats why so i got my other phone nope thats not it so i got the jailbroken one and got the app sync to allow unsigned code nope no go can u help?

[orchiha]

Has this been resolved yet? I am having the same issue running with OS 10.9.

[ike185]

Same problem at my end.

[chourobin]

Hey all, I got it working for me. I was running into the same issues described above. I suspect my problem was I had duplicate identities (i.e. certificates) in my keychain. Here's how I resolved:

• Go into Keychain and delete all the related certificates
• Quit Xcode, Re-launch Xcode and let it automatically download the certs again. This time hopefully you'll just have 1 valid cert.
• Go through iOS App Signer steps (making sure you choose the correct signing identity and the matching provisioning profile via app identifier)

Works smoothly thereafter. Good luck.

[tixastronauta]

@chourobin That was it! It also worked for me. Thank you very much!

[greeneggswitspam]

@chourobin did you delete all of your certificates? I deleted 1 duplicate I had but it still isn't working for me.

[Beachiie]

Still isn't working for me.. And I've tried everything.

[ady199]

Same problem for me and I've deleted all my certificates! I'm running it on Sierra

Help!!!!!

[ike185]

Yep, also the same at my end. I gave up till a fresh idea to try out comes my way.

[light122]

I have the same issue with "codesigning error". I have a $99 paid developer membership. I performed all the steps recommended in DanTheMan827 steps below, but the issue persists. Is there a way to fix this? I am trying to reload Kodi onto my iPAD after upgrading to IOS 10.0.2 (and Mac to Sierra), as it no longer works. Thanks for any help available.

DanTheMan827 recommended steps from another entry: Go into Xcode and delete your account from Preferences

Go to ~/Library/MobileDevice/Provisioning Profiles in finder and delete the files within

Go into keychain and delete any personal certificates mentioning Mac Developer, iOS Developer, etc

Add your account back into Xcode and choose to revoke the existing certificate

You'll have to re-generate any provisioning profiles since the previous ones were tied to the now revoked certificate and are now invalid

And also, don't manually trust the developer certificates... that breaks code signing completely since codesign won't trust it..

[DanTheMan827]

Try opening terminal and run the following command

xcode-select --install

[light122]

Brilliant!!! You are my hero. Why did this work, i.e., what was the “hangup”? Thanks again.

On Oct 10, 2016, at 9:06 AM, DanTheMan827 notifications@github.com wrote:

Try opening terminal and run the following command

xcode-select --install — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/DanTheMan827/ios-app-signer/issues/16#issuecomment-252666381, or mute the thread https://github.com/notifications/unsubscribe-auth/AVsjpLniAk4RpY0PSzdZZlfIHjdMXWJpks5qymKigaJpZM4ID-NG.

[ike185]

@light122 Thanks! Your solution worked for me. Am back on.

[greeneggswitspam]

@light122 @DanTheMan827 worked for me as well ! I'm back watching movies and shows on kodi!! Thanks a lot

[DanTheMan827]

@light122 Sorry, I've just been busy with other things...

I'm guessing a MacOS system update/upgrade removed the Xcode developer tools or that they were never installed...

That command tells the system to install them

[Beachiie]

This is very frustrating as I did everything according to @light122 and @DanTheMan827. I still got the same error result. Can anyone please tell me what has gone wrong?

[ike185]

Yeah you know what. I spoke too soon. Tried to sign another app and getting the same error too. Tried @light122 and @DanTheMan827 solution which worked the first time and still getting the same error. Very frustrating indeed.

[Brak01]

When I click start it starts to process the ipa, but then I get the following error:

ERROR VERIFYING CODE SIGNATURE! /var/folders/w7/h7_kf9191ts1bjth93rl7y700000gn/T/com.DanTheMan827.AppSigner.attQNDYW/out/Payload/Test App.app: invalid Info.plist (plist or signature have been modified) In architecture: armv7

I am even trying this on an app I copied from my phone and running it without doing any modifications to it, but still getting the same error.

Any advise how to resolve this issue?

[T1med0ut]

I met the same problem.I reset the certification but

[johnalex731]

Yup, getting the same problem, tried EVERY "Solution" I can find, with no luck

[Brak01]

WIll Dan ever reply to this?

[uiuco]

@Brak01 The problem that I have ever had.Reason is that when I test injection dylib, I didn't change the debug package to release package.Just change to release package is OK

[DanTheMan827]

@Brak01 Honestly, my app is just a GUI to the codesign command line utility.

If that's having problems signing a working app, my app won't magically make it work...

I've tested the app on all the OS versions I can think of, but it works every time...

The problem is almost always due to a misconfigured certificate or caused by selecting a mismatched certificate / provisioning profile pair...

I want to help, but short of hopping onto a computer with a problem for a more in-depth look, I can't re-create it...

[ginobean]

In my case, when I went into 'Keychain Access', under 'My Certificates', I noticed that I had a bunch of expired certificates. When I deleted all of the expired certificates under 'My Certificates', the iOS App Signer was able to work. You may want to add logic to your 'iOS App Signer' to skip over the expired certificates, as I think what may be happening is that your app is picking the first match, but this first match may actually be an expired certificate.

Xcode doesn't have a problem with this, suggesting that Xcode is automatically ignoring the expired certificates.

[zhao15]

I did everything according to above. I still got the same error result.

[frozt]

I had the same problem followed @ginobean comment and worked.

[jacrave]

The same error was being thrown for me. The issue was that I had 2 certificates, both valid, but upon further examination I found that 1 was revoked. I just had to delete it and then poof!, re-sign worked like a charm.

[fragno]

@chourobin cool, problem solved

[Joshab1177]

I have gone through multiple pages and followed all directions and nothing seems to work. I am running version 1.10 of App Signer, Version 10 of Xcode, and MacOS 10.13.6.

Xcode works all day long as far as detecting my certs. When I get to App Signer though it fails. Only thing I didn't try was the terminal command.

[wessidetempest]

So I deleted certs that were outdated and were not relevant anyway. All of the remaining My Certificates and Certificates have expiration dates in the future and are set to Trust: System Default. The only certification that I question has my name (global user name for computer) and the warning says: "This certificate has not been verified by a third party". Is that the potential issue?

[AdamMeyerTech]

I just wanted to say I am a complete noob at this and I just created an account to tell everything this process DOES work. Thank you so much!!

There was some fiddling around and the "+" on the last step isnt clear which "+" but on the whole it works.

THANK YOU DAN!!!!!