vsce create-publisher returns 401

[SamVerschueren]

I'm trying to create a publisher with a Personal Access Token but it fails to create it.

Error: Failed Request: Unauthorized(401) - https://app.market.visualstudio.com/_apis/gallery

[SamVerschueren]

Resolved the issue. The reason for returning 401 was that I didn't set the Accounts setting to all accessible accounts.

[amamut]

Adding a link to explain what this means as I googled this issue and landed here. No real explanation was given as how to enable this setting.

https://code.visualstudio.com/docs/tools/vscecli#_common-questions

[joaomoreno]

Thanks, @amamut!

Ping @waderyan: we really need SEO on our docs.

[waderyan]

@pjmeyer see above. Could use your help on improving SEO holistically for the site.

[Sequoia]

I'm struggling with this now, can't figure out what I'm supposed to enter as publisher for create-publisher and the docs all link in a circle 😦

[joaomoreno]

Hi @Sequoia, sorry to read that! Could you get a hold of a Personal Access Token? Once you do, you can call vsce create-publisher publishername to create it. Do you see any errors?

[Sequoia]

@joaomoreno Yes I have one, what i don't know is what to enter for publishername. Is it my "Team" name? An arbitrary string? I just keep getting 401 with no additional info.

[Sequoia]

Here's my "team" URL: https://34ks.visualstudio.com/

[npruehs]

Same here.

OS Version: Windows 10 Home 10.0.10538

VS Team Services Access Token Details:

Output:

C:\Users\Nick\Desktop\pony>vsce create-publisher npruehs
Publisher human-friendly name: (npruehs)
Personal Access Token: ****************************************************

Error: Failed Request: Unauthorized(401) -

[joaomoreno]

@npruehs This issue is closed.

Are you sure you created your PAT for all accessible accounts?

A: One easy mistake to make when creating the PAT (Personal Access Token) is to not select all accessible accounts in the Accounts field dropdown (instead selecting a specific account). You should also set the Authorized Scopes to All scopes for the publish to work.

[Sequoia]

@joaomoreno this bug should be migrated to the VSCode Extension platform/server repo; this is a UI bug in the server's response.

Expected

401 Unauthorized. If you are receiving this response on your own account, see faq.vscode.biz/#vsce-unauthorized

User is given some instruction on how to remedy this 👉🏼_common_👈🏼 issue with the peculiarities of the MSFT/VS permissions system that are frequently confusing to new users.

Actual

401 unauthorized

User is given no help, it appears they entered something wrong at the command line (whereas in fact the issue is with server account settings). You try to fix it, checking your credentials and retrying several times, to no avail. 😿

[Sequoia]

Or perhaps the help message should come from vsce upon 401? Either way, the user should be given some sort of guidance to help them handle this issue, which is a roadblock in particular for new users.