-
Notifications
You must be signed in to change notification settings - Fork 14
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
Submit failed for all browsers #2
Comments
Hey, sorry for the delay in getting back to you on this. Regarding Opera, could you try running it with Regarding Firefox, the error indicates that the string web-ext sign --source-dir <source-dir> --api-key $WEXT_SHIPIT_FIREFOX_JWT_ISSUER --api-secret $WEXT_SHIPIT_FIREFOX_JWT_SECRET Regarding Chrome, what did you do to make it work? I'd be happy to take steps to implement better error messages and tips on how to move forward 🙌 |
So I tried sumitting a new version today. About firefox, I still can't make it work. Now I get:$ shipit firefox BrowserExtension \ Building extension...Server response: Version already exists. (status: 409) × Error: Command failed: D:\Projects\ConstructAddonInstaller\Installer\node_modules\@wext\shipit\node_modules\.bin\web-ext sign --source-dir BrowserExtension --api-key user:13822079:21 --api-secret 1a977c386cced1018079367a2aa2ec0ebba921380dce194e51c65b347784056b Building web extension from D:\Projects\ConstructAddonInstaller\Installer\BrowserExtension Using previously auto-generated extension ID: {f0039c12-d785-4cf5-9504-a23f44f77996} FAILWebExtError: The extension could not be signed Error: Command failed: D:\Projects\ConstructAddonInstaller\Installer\node_modules@wext\shipit\node_modules.bin\web-ext sign --source-dir BrowserExtension --api-key user:13822079:21 --api-secret 1a977c386cced1018079367a2aa2ec0ebba921380dce194e51c65b347784056b WebExtError: The extension could not be signed
error Command failed with exit code 1. About chrome, what I did is just waiting before the previous extension was approved AND launching the command from a separated command prompt (the one integrated inside my IDE never worked) |
I don't think so, not a single of my versions are approved, and I have submitted quite a few using this tool 😆 it seems like they are super slow on reviewing 😞
Did you bump the version in your manifest? It seems to think that that version is already uploaded. I can recommend generating the version using this package: https://www.npmjs.com/package/utc-version |
Yeah they review manually. When it's approved first, it's super slow but it seems better once your have it accepted for the first time My bad, I couldn't separate the log between FF and Opera so I done it again using FF to have a clear log ^^ Here is the real log: https://hastebin.com/apitunufum.tex |
Hmm, that's interesting, could you try running the following command? If this gives an error as well, we'll probably need to raise an issue with the web-ext tool web-ext sign --source-dir BrowserExtension --api-key $WEXT_SHIPIT_FIREFOX_JWT_ISSUER --api-secret $WEXT_SHIPIT_FIREFOX_JWT_SECRET It probably will, since that is pretty much what this tool invoked. Would you mind opening an issue here: web-ext |
Yeah it gives an error as well.. https://hastebin.com/ajurokanop.tex |
EDIT: Chrome now works
Chrome failed with: ``` Response code 400 (Bad Request) { "error": "invalid_request", "error_description": "Parameter not allowed for this message type: redirect_uri" } Error: Command failed: D:\Projects\ConstructAddonInstaller\Installer\node_modules\@wext\shipit\node_modules\.bin\webstore upload --source BrowserExtension --extension-id xxx --client-id xxx --client-secret xxx --refresh-token xxx --auto-publish ```Firefox failed with:
(all other steps are successfull)
Opera failed with:
The text was updated successfully, but these errors were encountered: