Android fastlane supply failing all time, cannot parse json file

Bitrise Build Issue Report template

Description of the issue

All time have a problem with fastlane step, with action supply.
Cannot parse JSON key file, obtained from google play service account. This JSON was obtained and never edited. It is absolutely valid. At my local machine action supply works perferctly, but in bitrise it’s failing all time.
I’m getting

‘ce407029dc78.json’ doesn’t seem to be a JSON file
You passed invalid parameters to ‘supply’.
Check out the error below and available options by running fastlane action supply
Invalid default value for json_key, doesn’t match verify_block

Environment:

Where did the issue happen?

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

Which build Step causes the issue and which version of the step?

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES/NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES/NO
  • If you have multiple different build configurations (workflows), does the issue affect all/more than one? : YES/NO
  • If it’s an issue which happens sporadically, what’s the frequency? (e.g. Once a day ; about x% of the builds) :
  • Does upgrading the build Step to the latest version help? : YES/NO
  • When did the issue start? :

Linux/Android stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

Other stacks

Can it be reproduced by running the build locally with our CLI ( https://www.bitrise.io/cli ), after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )?

Build log

Please attach the build log (you can download the build log from the build’s page, once the build is finished, using the “Download log” button - floating at the bottom right corner of the log viewer), or if you can’t attach the whole log then send the full log through a private channel (e.g. email - https://www.bitrise.io/contact ), with a link to the related GitHub issue.

Questions is, are you sure that the JSON file is actually there? Is that in your repository? Or you retrieve it on bitrise.io from somewhere else?

Please follow this guide and let us know how it goes:

yes, it is in the repo from which i’m building

Please follow this guide and let us know how it goes:

Followed all this steps, runned via CLI and got the same error as on bitrise.io

JSON file is absolutely valid, i’ve checked with JSON lint
And when I’m running locally on CLI only Fastlane - its lane working perfectly, but when I try to integrate fastlane as step to bitrise - its not working all time

Which step do you use for running fastlane? Please copy paste the step’s full log output, with the step header which includes the ID, and with the footer which includes the run time.

Or send us the full build log or the build’s url in email or through the onsite chat

url https://www.bitrise.io/build/2bd30971f857d520

When you run this directly through fastlane, from which directory you run the fastlane command?

Do you run it from the ./platforms/android/fastlane directory? In your bitrise config you specified that (./platforms/android/fastlane) as the working directory for fastlane.

on my local machine I’m running fastlane command from .platforms/android directory (android directory contains my project and fastlane folder)

Then please change the workdir in your config to point to that directory, instead of the fastlane directory inside that. That should work :wink:

1 Like

thank you so much, Victor! It works! :relaxed:

1 Like