Vscode-vsce: Bad Request(400) - Value cannot be null. (extensionPackage)

Created on 6 Apr 2017  路  9Comments  路  Source: microsoft/vscode-vsce

When I do a publish, a error comes as bellow:

Error: Failed Request: Bad Request(400) - Value cannot be null.
Parameter name: extensionPackage

This extension has been published successfully some days ago, and I just edit the function code for the new publishing.
Since no details to check, I am puzzled by this case.

needs more info

Most helpful comment

@FFengIll , did you get a chance to try @joaomoreno 's suggestion of attempting from a different machine?

From the error, it seems the vsce on your system is still using the older version of the lib (5.x.x ), even though vsce itself is the latest version, 1.20.0 ; would you please share the version details of the vso-node-api package that is being used by vsce on your system ? On a Windows system, this would be found inside C:\Users\USERNAMEappdataRoaming\npmnode_modules\vscenode_modules\vso-node-apipackage.json : there would be a version entry as below :
"version": "6.1.2-preview"

Would you please share this info? Please also share the output of "npm info vsce"

If it turns out the lib version being used is older (5.x.x ), would you please try to force upgrade :

npm uninstall -g vsce
npm install -g vsce -f

If, however, the lib version being used looks good (6.1.2-preview), would you please share a network trace using Fiddler or CharlesProxy to help debug further?

All 9 comments

What version do you have? vsce --version

here you are

vsce --version
1.20.0

cc @hamenon @modigrv

@FFengIll Does it repro every time? Can you try from another machine? What does vsce ls return?

Are your sources in GitHub so I can give it a try?

@FFengIll , did you get a chance to try @joaomoreno 's suggestion of attempting from a different machine?

From the error, it seems the vsce on your system is still using the older version of the lib (5.x.x ), even though vsce itself is the latest version, 1.20.0 ; would you please share the version details of the vso-node-api package that is being used by vsce on your system ? On a Windows system, this would be found inside C:\Users\USERNAMEappdataRoaming\npmnode_modules\vscenode_modules\vso-node-apipackage.json : there would be a version entry as below :
"version": "6.1.2-preview"

Would you please share this info? Please also share the output of "npm info vsce"

If it turns out the lib version being used is older (5.x.x ), would you please try to force upgrade :

npm uninstall -g vsce
npm install -g vsce -f

If, however, the lib version being used looks good (6.1.2-preview), would you please share a network trace using Fiddler or CharlesProxy to help debug further?

@joaomoreno
Actually, it does not work in another machine, since all of our machine work with same env.
But I found the reason with @amitramesan 's suggestion: vso-node-api version is 5.x.x with vsce 1.20.

After the upgrade, it works now.
Thx.

Awesome :-)

@FFengIll Would you please also share for investigation some information about your environment ;

  1. What OS/Version and SKU/Distribution?
  2. What is the NodeJs version?

Thanks,
Amit.

Env. information as bellow:

Window 10 x64 Home version 14393
nodejs 6.10.1

normal with

  • vsce 1.20
  • vso-node-api 5.1.2
  • vscode 1.10.2

abnormal with

  • vsce 1.20
  • vso-node-api 5.1.2
  • vscode 1.11

normal (recovered) with

  • vsce 1.20
  • vso-node-api 6.1.2-preview
  • vscode 1.11 (and 1.11.1)

Pls feel free to let me know if any others are required.

Thank you, @FFengIll ; this really helps. We'll reach out if we need more info.

Was this page helpful?
0 / 5 - 0 ratings