Clever Geek Handbook

How do you solve iPhone 'signature is valid but not trusted' error?

Finally, MGTwitterEngine material for

compile (by setting the headers search paths to / usr / include / libxml 2 iphoneos3.0 / usr / lib / libxml2)

And a link (by removing the Twitter LibXML Parsers browser code and assigning the libxml2.2.dylib weak role in Targets: Link Binary With Libraries).

But when I do Build and Go to iPhone (not simulator) I get this error:

"This provisioning profile does not have a valid signature (or has a valid but unreliable signature)."

I followed the official Apple Developer process for getting certified and providing resources, etc. Obviously, I did something wrong. Has anyone come across this problem or have any ideas on how to solve it?

+2


source to share


5 answers


Things to check:



  • In Keychain Access, make sure you have a Code ID (public and private keys and a certificate called "iPhone Developer: Your Name"
  • In your Info.plist make sure your bundle id matches your app id created in dev portal
  • Make sure you have installed .mobileprovision (from Terminal> open x.mobileprovision)
  • In the dev portal, make sure your provisioning profile has its certificate, your app ID, and your device. If it is not, fix it and re-download and reinstall your provisioning profile.
  • Follow the instructions carefully when creating the certificate. One day, in Keychain Access, when I went to request a certificate, I had something else selected in the list pane and so it generated the wrong kind of certificate. Make sure that nothing is selected in the list when doing this part.
+4


source


Restarting Xcode might work too ... (Work for me a couple of times)



+1


source


Troy It looks like the problem is that you don't have a key pair bound to your setup profile. It's hard to say for sure, but it's my best guess.

If so, I worked in a similar situation - you need to either generate a private key using the iphone development portal in the same account your boss used, and then add that new key to secure with which you are building. OR you can force your boss to export the key he generated when he created the provisioning profile - he can export it from the keychain and provide him with a password that will allow you to install it, but protect it from anyone who installs it.

0


source


I think the fifth time is the charm. I basically deleted the certificate and init file, etc. and I was completely finished. Viola! Now for those pesky memory leaks! :-) Oh Java, what are you for, Java? (and your May garbage collection!)

0


source


One of the things I tried and worked for me was to reset the keychain access http://support.apple.com/kb/TS1544

0


source






More articles:


All Articles