Open rvanderlinden opened 1 month ago
I have made some progress since:
build
and deploy
in a single workflow job.build + upload artifact
and download artifact + deploy
steps into different workflow files this problem pops up. I kept all relevant parameters equal between the working single workflow and multiple workflow approach and the error mentioned above remains.tar
of the output directory of the apk, which contains some other files (output-metadata.json), and which allows me to untar it in the exact same structure as in the single workflow approach. I was hoping this would solve something, but unfortunately the same error still occurs.serviceCredentialsFile
param to validate the issue is not related to the serviceCredentialsFileContent
.Can this be related to file access permissions somehow?
Unfortunately I was not able to make any further progress. Instead we decided to try out firebase_app_distribution
in Fastlane, which does work with the reusable workflow outlined above.
I'm not sure what is holding back the reusable workflow approach for this action, but if someone thinks they may have a way to resolve it, please let me know so I can try it out. Meanwhile we'll opt for the Fastlane approach.
Hi,
I'm trying to use this action in a reusable workflow to upload an apk to Firebase App Distribution. Unfortunately I keep getting an issue.
The error (if I set
debug: true
there is no additional output):The action in use:
Considering the error is related to parsing JSON and the
serviceCredentialsFileContent
is the only JSON submitted by me, I validated the service account, the key and the secrets. I have a similar setup for Play Store distribution (with a private JSON key) that is working so I'm unsure what I'd be doing wrong here.That brings me to my question: Is there any way I could get more information about the cause of the problem? I feel like the error
Unexpected token < in JSON at position 0
is not related to theserviceCredentialsFileContent
, but I need more feedback to validate that. Any ideas how I can move forward? Thanks!Edit: I noticed on another issue that this error may be related to a very large apk, which is not the case here (about 10 MB).
Full workflow: