-
Notifications
You must be signed in to change notification settings - Fork 41
SSL Error on push using PEM development certificate #5
Comments
That looks weird. Here is the code, which generates the profile for you: cert_manager.rb How is it different from what you do when you create one manually? |
These are my manual steps in creating a cert:
I'm not too great on openssl but it would seem my openssl command is differing in that I'm omitting the -passin flag and including the -clcerts flag |
It looks like there is some problem with your private key. What does the QuickLook plugin tell you (if you have it installed)? |
Okay, it looks like I have the same problem when running it. I seem to have broken it somehow - it worked before. I assume this is somehow related to the temporary Keychain. |
This is fixed with the latest release: https://github.com/KrauseFx/PEM/releases/tag/0.2.0 Please update using |
Hey, just testing this now and I get an error when generating the .cer file.
|
Oh, looks like |
This is not related to the original issue. I'm currently working on a fix of this problem. |
Could you please download the current version as zip, and run |
This issue was migrated to fastlane/fastlane#2845. Please post all further comments there.
|
I generated a PEM certificate using the instructions in the README and all seemed to work ok. However, when I try to push the notification using the pem development certificate if receive the following error in my terminal.
This is with the ruby houston gem:
I also tried with the ruby grocer gem to be sure it's not a ruby issue and received the same error.
My hand generated pem file works just fine.
The text was updated successfully, but these errors were encountered: