-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--use-submission-api results in HTML response with "Oops! We can’t find that page" #2579
Comments
cc @eviljeff |
this pathname is wrong - should be |
my best guess is the @karlicoss can you confirm by adding |
The URL is constructed at web-ext/src/util/submit-addon.js Line 90 in 421f429
new URL('addons/', 'http://a/b/v5').href -> http://a/b/addons/ without /v5 . We should ensure that / is appended to the path if it is missing.
We have a unit test checking the base URL at
|
@eviljeff can confirm adding the base URL worked -- successfully uploaded a new version to the unlisted channel, and web-ext waited for the approval |
I could submit without errors listed and unlisted versions using --amo-base-url=https://addons-dev.allizom.org/api/v5 |
Is this a feature request or a bug?
Bug.
What is the current behavior?
So far I've been successfully using
sign
and publishing my addon without--use-submission-api
.I've decided to give this flag a go:
My extension's manifest version is 2 (not sure whether this matters). I also had to add extension ID to the manifest, otherwise web-ext complained.
However this resulted in a cryptic error. I nailed it down to this line
https://github.com/mozilla/web-ext/blob/master/src/util/submit-addon.js#L246
Somehow instead of JSON, I got a html page with the following content
I added a bit more debug logging to web-ext and this is the fetch call that fails:
Anything I'm doing wrong?
What is the expected or desired behavior?
Extension is uploaded to addons.mozilla.org
Version information
The text was updated successfully, but these errors were encountered: