An Error Occurred Cannot Parse Message.json File From Uploaded Package
from GoogleSign inHidden fieldsSearch for groups or messages
Correia
about "message.json" Starred by 1 user Reported by mahem...@gmail.com, Feb 22 2013 https://bugs.chromium.org/p/chromium/issues/detail?id=177629 Back to list Status: Assigned Owner: mkearney@chromium.org Components: Platform>Extensions OS: Mac Pri: 2 Type: Bug Hotlist-Recharge Hotlist-Recharge-Stale Via-Wizard Documentation Sign https://visionmedia.github.io/superagent/ in to add a comment UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17 Steps to reproduce the an error problem: If locale is specified, but messages.json is wrong, developer dashboard says: "An error occurred: Cannot parse message.json file from uploaded package." when uploading zip file. What is the expected behavior? What went wrong? Should say "messages.json" not "message.json" WebStore page: http://geek.mgorecki.net/index.php/2011/02/11/chrome-webstore-message-json-issue/ Did this work before? N/A an error occurred Chrome version: 24.0.1312.57 Channel: n/a OS Version: OS X 10.7.5 Reported at http://geek.mgorecki.net/index.php/2011/02/11/chrome-webstore-message-json-issue/ and I saw it myself today. Comment 1 by petewil@chromium.org, Feb 25 2013 Processing Labels: -Type-Bug Type-Documentation Owner: mkearney@chromium.org Meggin - could you please find the appropriate docs person to route this to? Thanks! Comment 2 by petewil@chromium.org, Feb 27 2013 Processing Status: Assigned Project Member Comment 3 by bugdroid1@chromium.org, Mar 10 2013 Processing Labels: -Feature-Extensions -Type-Documentation Documentation Type-Bug Cr-Platform-Extensions Comment 4 by lafo...@chromium.org, Sep 23 2015 Processing Labels: Hotlist-Recharge Hotlist-Recharge-Stale This issue likely requires triage. The current issue owner maybe inactive (i.e. hasn't fixed an issue in the last 30 days). It has also not been modified in a year (prior to this update). Thanks for helping out! -Anthony ► Sign in to add a comment About Monorail Feedback on Monorail Terms Privacy
name: 'Manny', species: 'cat' }) .set('X-API-Key', 'foobar') .set('Accept', 'application/json') .end(function(err, res){ if (err || !res.ok) { alert('Oh no! error'); } else { alert('yay got ' + JSON.stringify(res.body)); } }); Test documentation The following test documentation was generated with Mocha's "doc" reporter, and directly reflects the test suite. This provides an additional source of documentation. Request basics A request can be initiated by invoking the appropriate method on the request object, then calling .end() to send the request. For example a simple GET request: request .get('/search') .end(function(err, res){ }); A method string may also be passed: request('GET', '/search').end(callback); ES6 promises are supported. Instead of .end() you can call .then(): request('GET', '/search').then(success, failure); The node client may also provide absolute urls: request .get('http://example.com/search') .end(function(err, res){ }); DELETE, HEAD, POST, PUT and other HTTP verbs may also be used, simply change the method name: request .head('/favicon.ico') .end(function(err, res){ }); DELETE is a special-case, as it's a reserved word, so the method is named .del(): request .del('/user/1') .end(function(err, res){ }); The HTTP method defaults to GET, so if you wish, the following is valid: request('/search', function(err, res){ }); Setting header fields Setting header fields is simple, invoke .set() with a field name and value: request .get('/search') .set('API-Key', 'foobar') .set('Accept', 'application/json') .end(callback); You may also pass an object to set several fields in a single call: request .get('/search') .set({ 'API-Key': 'foobar', Accept: 'application/json' }) .end(callback); GET requests The .query() method accepts objects, which when used with the GET method will form a query-string. The following will produce the path /search?query=Manny&range=1..5&order=desc. request .get('/search') .query({ query: 'Manny' }) .query({ range: '1..5' }) .query({ order: 'desc' }) .end(function(err, res){ }); Or as a single object: request .get('/search') .query({ query: 'Manny', range: '1..5', order: 'desc' }) .end(function(err, res){ }); The .query() method accepts strings as well: request .get('/querystring') .