Plasmo BPP "keys" missing on publish in CI

By Kaveh Alemi·Latchkey

Plasmo BPP publishes a built extension to the stores using a keys JSON of per-store credentials. Without that keys input, BPP has nothing to authenticate with and the publish step fails.

What this error means

The BPP publish step fails reporting that the keys input was not provided or that no store credentials were found.

Error: No keys provided. Set the "keys" input with your store credentials JSON.
The browser-platform-publish action requires keys to submit.

Common causes

The keys input was not passed from secrets

The publish action ran without its keys input, so it has no Chrome/Firefox/Edge credentials to submit with.

Malformed keys JSON

The provided keys value is not valid JSON or is missing the store section being targeted.

How to fix it

Provide the keys JSON from a secret

1. Build a keys JSON containing each target store credential block.
2. Store it as a single CI secret.
3. Pass it as the keys input to the publish action.

- uses: PlasmoHQ/bpp@v3
  with:
    keys: ${{ secrets.BPP_KEYS }}

Validate the keys JSON shape

Confirm the JSON parses and contains the section for the store you are publishing to.

node -e "JSON.parse(process.env.BPP_KEYS)"

How to prevent it

• Keep the BPP keys JSON in a single CI secret.
• Validate the keys JSON parses before publishing.
• Include a credential block for every target store.

Frequently asked questions

Related guides

References

• Node.js documentation
• npm CLI documentation
• GitHub Actions documentation