Issue metadata
Sign in to add a comment
|
Server returns 503 when uploading extension
Reported by
ihvarf...@gmail.com,
Nov 5 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.28 Safari/537.36 Steps to reproduce the problem: Upload a new extension or a new version of an extension What is the expected behavior? The extension should be uploaded or a useful error message stating user error should be displayed. What went wrong? The server responds with 503. "(Lost connection to server)" and "An error occurred: please try again later." is shown on the page. WebStore page: https://chrome.google.com/webstore/developer/update Did this work before? Yes 2016-8-18 Chrome version: 55.0.2883.28 Channel: beta OS Version: Flash Version: Shockwave Flash 23.0 r0 There is a topic in the Chromium-Extensions-Announce group about this issue: https://groups.google.com/a/chromium.org/d/topic/chromium-extensions/ugBPmzmxmW8/discussion
,
Nov 5 2016
Hi -- The Chrome Web Store engineering team is investigating.
,
Nov 5 2016
This should be fixed now. Please re-open this bug and provide details if you are still experiencing upload problems.
,
Dec 1 2016
I'm seeing this issue again.
,
Dec 1 2016
@chris.davis, thanks for the report. The Chrome Web Store team is looking into it again.
,
Dec 1 2016
@chris.davis didn't provide much detail, but I happened to run into this same issue today. Not exactly the same as reported, but here are my details. I am having this issue both with uploading a Google Chrome application and a Google Chrome extension. However I am not getting a server response of 503, I am getting a 200 response but with an error message on the screen stating "An error occured: please try again later." The response body contains a field 'requestRejectedInfo' which is giving me a value of "agent_rejected". Any ideas on this? Is this a permissions issue, or is this actually a bug? I have never had issues uploading before today. Another developer on the team also states that he started experiencing the same issue starting yesterday.
,
Dec 1 2016
Yeah, I should have provided more details. After I posted I also checked the response and it's the same as ytok reported.
,
Dec 1 2016
Thanks for the extra details. I'll circle back here as soon as there's an update.
,
Dec 2 2016
This started working again for me this morning.
,
Dec 2 2016
Great -- yes the fix landed a few hours ago. Glad to hear it's working for you again. Please re-open if you experience further issues. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jawag@chromium.org
, Nov 5 2016Status: Started (was: Unconfirmed)