Replies: 2 comments
-
hello @vmlb13 I see you have overcome the previous error by removing the script entirely and adding build arguments with the auto-incremented built-in environment variable Now I'm noticing a different error on your latest build
This could also happen if you haven't provided any privacy policy to your app in the Google Play Developer Console. |
Beta Was this translation helpful? Give feedback.
-
Hi @dtrdic, yes I changed the approach for the automatic build versions from code magic. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
If you are looking for help, please confirm the following...
Which mobile framework are you using?
Flutter (Dart)
Steps to reproduce
I'm getting this error in my pre build script, I tried to change the private key several times and I also printed the private key from the environment variable, the content it's there and in the right format, but the issue seems to stay.
Error:
app-store-connect get-latest-app-store-build-number: error: argument --private-key: Provided value is not a valid PEM encoded private key
Failed to get the latest build number from App Store Connect.
Script:
Expected results
It's supposed to get the latest build number from the app store
Actual results
Error:
app-store-connect get-latest-app-store-build-number: error: argument --private-key: Provided value is not a valid PEM encoded private key
Failed to get the latest build number from App Store Connect.
Build id (optional)
6699350e3c6f7f72927a91f0
Beta Was this translation helpful? Give feedback.
All reactions