Getting error: invalid curve name for app_store_connect_api_key

[itsnaidu]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

Getting this invalid curve name while calling lane having app_store_connect_api_key.

Command executed

app_store_connect_api_key

Complete output when running fastlane, including the stack trace and command used

 [REPLACE THIS WITH YOUR INFORMATION] 

Environment

 [REPLACE THIS WITH YOUR INFORMATION] 

[fastlane-bot]

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

[itsnaidu]

Sorry, I didn't get this.

Are you talking about how I am setting the environment variables? I have a .env file in my repo where I am storing all the values. But, I got this error without setting the value from ENV too.

[charrhia]

I receive this error when my key_content (contents of the .p8 file) is improperly formatted for submission: http://docs.fastlane.tools/actions/app_store_connect_api_key/#app_store_connect_api_key. If I don't do a new line '\n' at the beginning and end of the key then fastlane will error saying it's not valid. Check for white characters or anything that might be throwing off that key value.

[kimar]

I also saw this error, fore me it helped to wrap the key in my .env e.g. instead of

ITC_KEY=-----BEGIN PRIVATE KEY-----\nABCEDF…\n-----END PRIVATE KEY-----

I wrapped the string value in quotes:

ITC_KEY="-----BEGIN PRIVATE KEY-----\nABCEDF…\n-----END PRIVATE KEY-----"

[jeffmon]

That fixed this issue for me, @kimar. Thanks!

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[fastlane-bot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

[xanderbuck]

@kimar's answer is what fixed this for me. I didn't have the correct format of the string with the \n new line characters

[Shayokh144]

By using
ENV['APP_STORE_CONNECT_API_KEY_KEY_ID'] in place of ENV["API_KEY_ID"]
ENV['APP_STORE_CONNECT_API_KEY_ISSUER_ID'] in place of ENV["ISSUER_ID"]
ENV['APP_STORE_CONNECT_API_KEY_IS_KEY_CONTENT_BASE64'] in place of ENV["APPSTORE_CONNECT_API_KEY"]
fixed my problem. I was using ruby fastlane not swift fastlane

[raladdin]

What fixed it for me is wrapping the key in quotes and including all of the /n (before and after the key but also the line breaks within the key).

[LydGol90]

Hi, in case it is helpful for anyone, the issue for me was it was looking in the wrong directory for fastlane. I think you might be facing the same issue because it says bundler: failed to load command: fastlane, which mine also did. The issue for me was that I was using a ruby version installed via rbenv but I had previously installed gems using system ruby. You could check gem env home and which fastlane to see if they are using the same ruby directory.