Submit fails both stores

[consciousweb]

Describe the bug

trying to use submit, and submission fails both stores. I have init both and have a .env.submit

Chrome: fails for unknown reason

Firefox: fails because it requires a string for config.manifest.content_security_policy instead of an array like Chrome v3. I used the -c param with zip and a custom firefox config and it submit correctly. Is there some way WXT has built in to handle this compatibility issue more smoothly that I'm missing?

Cli Command:

wxt submit \          
  --chrome-zip .output/[package]-[version]-chrome.zip \
  --firefox-zip .output/[package]-[version]-firefox.zip --firefox-sources-zip .output/[package]-[version]-sources.zip \

Logs:

ℹ Publishing Extension                                                                                     12:05:41 PM
✖ [PUT] "https://www.googleapis.com/upload/chromewebstore/v1.1/items/[chrome id]": 403 Forbidden
✖ [POST] "https://addons.mozilla.org/api/v5/addons/addon/[firefox id]/versions/": 400
  Bad Request

Request: https://www.googleapis.com/upload/chromewebstore/v1.1/items/[chrome id]
Response: {
  "_data": {
    "error": {
      "code": 403,
      "message": "Forbidden",
      "errors": [
        {
          "message": "Forbidden",
          "domain": "global",
          "reason": "forbidden"
        }
      ]
    }
  }
}
[12:05:41 PM]  ERROR  [PUT] "https://www.googleapis.com/upload/chromewebstore/v1.1/items/[id]": 403 Forbidden

  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async $fetch2 (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/ofetch/dist/shared/ofetch.d8adb063.cjs:322:15)
  at async CwsApi.uploadZip (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:2920:5)
  at async ChromeWebStore.submit (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:3010:5)
  at async Task.task [as taskFn] (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:3511:11)
  at async Task.run (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/listr2/dist/index.cjs:2143:11)
Request: https://addons.mozilla.org/api/v5/addons/addon/[firefox id]/versions/
Response: {
  "_data": {
    "upload": [
      "Upload is not valid."
    ]
  }
}
[12:06:14 PM]  ERROR  [POST] "https://addons.mozilla.org/api/v5/addons/addon/[firefox id]/versions/": 400 Bad Request

  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async $fetch2 (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/ofetch/dist/shared/ofetch.d8adb063.cjs:322:15)
  at async AddonsApi.versionCreate (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:3262:12)
  at async FirefoxAddonStore.submit (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:3333:22)
  at async Task.task [as taskFn] (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/publish-browser-extension/dist/cli.cjs:3511:11)
  at async Task.run (/Users/[user]/.nvm/versions/node/v20.9.0/lib/node_modules/wxt/node_modules/listr2/dist/index.cjs:2143:11)

 ERROR  Submissions failed: 2      

Reproduction

n/a

Steps to reproduce

No response

System Info

System:
    OS: macOS 12.6.2
    CPU: (10) arm64 Apple M1 Max
    Memory: 79.53 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    Yarn: 1.22.21 - ~/.nvm/versions/node/v20.9.0/bin/yarn
    npm: 10.5.1 - ~/.nvm/versions/node/v20.9.0/bin/npm
    Watchman: 2023.09.04.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 130.0.6723.70
    Firefox: 131.0.3
    Safari: 15.6.1
  npmPackages:
    wxt: ^0.19.9 => 0.19.9

Used Package Manager

npm

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[aklinker1]

For chrome, did you create a refresh token using wxt submit init?

For Firefox, I think there's a bug where WXT doesn't automatically convert MV3 content_security_policy to it's MV2 form.

[consciousweb]

Yes and the refresh token is saved in the .env.submit

…

On Thu, Oct 31, 2024 at 9:14 AM Aaron ***@***.***> wrote: For chrome, did you create a refresh token using wxt submit init? For Firefox, I think there's a bug where WXT doesn't automatically convert MV3 content_security_policy to it's MV2 form. — Reply to this email directly, view it on GitHub <#1124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLFB3LTTXO7P3ABR7KZ4BDZ6JCLTAVCNFSM6AAAAABQ2O2GACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJQGEZTOMBTGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[aklinker1]

Are you using the right extension ID? Does a dry run pass? wxt submit --dry-run. Works fine for me, so something has to be wrong with your credentials. Did you create the gcp credentials in the same account that has access to the CWS?

[consciousweb]

Dry run runs fine. Check OP, firefox works if you specify a separate config. Chrome does not work, cws creds are correct.

…

On Wed, Nov 13, 2024 at 12:06 PM Aaron ***@***.***> wrote: Are you using the right extension ID? Does a dry run pass? wxt submit --dry-run. Works fine for me, so something has to be wrong with your credentials. Did you create the gcp credentials in the same account that has access to the CWS? — Reply to this email directly, view it on GitHub <#1124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLFB3LLCT2KCADAFBSGTW32AOPMJAVCNFSM6AAAAABQ2O2GACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGQ4TKMZVHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Timeraa]

Does it work if you upload them yourself? I had an issue once with Firefox's validation that publish didn't show for some bizzare reason