Giters

kevin-david / promote-play-release

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unexpected token . in JSON at position 0

flameshikari opened this issue · comments

commented

Hello!

The action fails with Unexpected token . in JSON at position 0
JSON is 100% valid (checked with jq)
Is there anything else I can provide to fix the problem?

The workflow step

...

- uses: kevin-david/promote-play-release@v1.0.0
  with:
    service-account-json-raw: service_account.json
    package-name: [REDACTED]
    inapp-update-priority: 5
    user-fraction: 1.0

...

service_account.json (edited)

{
  "type": "service_account",
  "project_id": "[REDACTED]",
  "private_key_id": "[REDACTED]",
  "private_key": "[REDACTED]",
  "client_email": "[REDACTED]",
  "client_id": "",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "[REDACTED]"
}
commented

service-account-json-raw takes a string containing JSON text, not a file name. The idea is that you provide the JSON as a secret for your project

commented

service-account-json-raw takes a string containing JSON text, not a file name. The idea is that you provide the JSON as a secret for your project

Ah, now I understand. Thanks for the clarification!

One more question: does this Action provide release notes (like 'whatsNewDirectory' input from r0adkll/upload-google-play)?

commented

I don't think so. Is that something you can/want to configure when promoting releases? I'd imagine your alpha/beta release would already have release notes, which would carry over to the new track

commented

I'd imagine your alpha/beta release would already have release notes, which would carry over to the new track

This is what I need. Will test later. Thanks again!