Action fails with ENOENT without specifying missing file

Hello, I get this output from my workflow:

##[error]ENOENT: no such file or directory, open
##[error]Node run failed with exit code 1

And my parameters are the following:

        serviceAccountJson: private_key.json
        packageName: it.riccardopersello.sigma
        releaseFile: build/app/outputs/bundle/release/app-release.aab
        track: internal

I check the existence of the aab file before calling this action. The full workflow is

on:
  push:
    branches: 
      - internal-release

name: Test, build and release APK on Google Play Store (internal branch)
jobs:
  build:
    name: Test, build and create APK
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - uses: actions/setup-java@v1
      with:
        java-version: '12.x'
    - uses: subosito/flutter-action@v1
      with:
        channel: 'stable'
    - name: Flutter upgrade
      run: flutter upgrade
    - name: Flutter get packages
      run: flutter pub get
    - name: Flutter test
      run: flutter test
    - name: Generate build number
      uses: einaregilsson/build-number@v2 
      with:
        token: ${{secrets.github_token}}
    - name: Print build number
      run: echo "Build number is $BUILD_NUMBER"
    - name: Flutter build signed appbundle
      env:
        KEYSTORE_PASSWORD: ${{secrets.KEYSTORE_PASSWORD}}
      run: flutter build appbundle --release --build-number $BUILD_NUMBER
    - name: Key to file
      env:
        KEY_JSON_CONTENT: ${{secrets.PLAY_STORE_JSON}}
      run: echo $KEY_JSON_CONTENT > private_key.json
    - name: Check bundle existence
      run: test -f build/app/outputs/bundle/release/app-release.aab && echo "Bundle exists"
    - name: Upload bundle to Play Store (internal channel)
      uses: r0adkll/upload-google-play@v1
      with:
        serviceAccountJson: private_key.json
        packageName: it.riccardopersello.sigma
        releaseFile: build/app/outputs/bundle/release/app-release.aab
        track: internal

How can I get a more detailed error report for the missing file?

[r0adkll]

I pushed an update out (v1.0.1 or continue using the v1 tag) that includes some improved debugging and runs some pre-condition checks to verify that your inputs exist, then prints the input back out if it fails

[r0adkll]

You are correct, those inputs are suppose to be optional, I added some checks to validate that the directory or file exists if you include them but it looks like those checks are tripping anyway. I’ll get these issues fixed and pushed, but I’m glad the action completes for you afterwards.