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.

[joaomoreno]

Agreed. Pushed a commit which guides users towards fixing this specific problem.

[npruehs]

Worked like a charm. Thanks all!

[Sequoia]

👏🏼👏🏼👏🏼👍🏼 thanks!!

[joshjg]

I get 401 here even though I set up the token for all accessible accounts. At a dead end here...

[joaomoreno]

@joshjg Have you tried picking another publisher name?

[joshjg]

@joaomoreno Yes, to no avail.

[joaomoreno]

@modigrv @hamenon Some help here?

[hamenon]

@joshjg could you give us some more info like the account name where you created the token and the publisher id you are looking to create? Might help us investigate further. If possible can you write to us at [email protected] we can have someone from the team debug the issue.

As a workaround you could create the publisher manually at http://marketplace.visualstudio.com/manage and upload the packaged vsix directly to get unblocked

[ipedrazas]

So, I'm in the same situation, trying vsce create-publisher and getting a 401.

I've just published the extension using @hamenon workaround 👏

Why don't you put this workaround in the docs?

[joaomoreno]

Added to the docs: microsoft/vscode-docs@5fad3ce

[ipedrazas]

I'm afraid the workaround only allows you to create a new extension but not to update one.

What happens if I delete my extension and publish a new version? how this affects users with the extension installed?

How can I debug vsce? I've tried both vsce login and vsce create-publisher and I've got the same error (401) in both cases.

[ipedrazas]

I've managed to update the extension using the very hidden option in the extension... If you point me to the GitHub repo of the marketplace I'd like to file an issue.

[andradei]

This is such a huge pain point to beginner extension devs. If it weren't for this issue thread, I'd be stuck.

Thanks for updating the documentation, I hope it lands soon.

[joaomoreno]

@hamenon There seems to be a lot of friction over here. Is there any way vsce can get the error message from the 401 through the use of vso-node-api?

[hamenon]

We did discover an issue with the PAT's that are issued by the VSTS Identity Service. This has now been fixed and the deployed on production. Note that only PAT's created in the last week or so are affected.

1. Existing users with Old PAT's (over a week old) can continue using them
2. Existing users who created new PAT's in the last week need to generate new PAT's
3. New users trying to create publishers can generate PAT now and get going.

[geddski]

So I just hit this trying to publish my first extension. Really have no idea what "which has access to all accessible accounts" means. What should I do from here?

[joshjg]

@geddski This is the option you're looking for:

[geddski]

Ah that worked. Thanks!
On Thu, Nov 17, 2016 at 6:59 PM joshjg [email protected] wrote:

@geddski https://github.com/geddski This is the option you're looking
for:
[image: screen shot 2016-11-17 at 8 57 58 pm]
https://cloud.githubusercontent.com/assets/21149010/20415795/aacee9ea-ad08-11e6-876c-63ea1c8f32ab.png

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfeioU8AjYqcROxfXyY41g6sQQALm-Xks5q_QZrgaJpZM4GQJRH
.

[AvraamMavridis]

I am trying the same but I dont have the all accessible acounts option...

[webjohnjiang]

i have get the same problem, and finally find the reason is "forget to change organization to all accoujnts when create token"

[toreaurstad]

Well, I am using an account at work and I had to enable a PAT for "All accessible organizations", which of course is similar to the case "All accounts". But it should be noted as a possible scenario.

[guitartsword]

vsce --version
1.66.0

The message is still not helping the user😢

I installed it today via npm i -g vsce

[zhohon]

vsce --version
1.66.0

The message is still not helping the user😢

I installed it today via npm i -g vsce

+1

[creaink]

vsce --version
1.66.0

The message is still not helping the user😢

I installed it today via npm i -g vsce

use vsce login and paste token is fine for me

[MaskRay]

Got the same unhelpful error message.

 ERROR  Failed request: (401)

% vsce --version         
1.67.1

On https://dev.azure.com/$myorganization/_usersSettings/tokens, changing the scope to "All accessible organizations" fixed the 401 problem.

[syyam]

Select this option from the dropdown.

[erlangparasu]

Thank you very much @hamenon

[vsTianhao]

It was a terrible mistake, I don't understand the meaning of choice “All accessible organizations” ,That seems to be the only choice , The other option doesn't seem to make any sense.

[ngarg-panw]

I have lost the existing token. The person who generated the token first time is no longer with the team. How can I associate a new token from a new account to existing publisher?
I tried creating a token from new account and it says:
ERROR Access Denied: abcxyzteam needs the following permission(s) on the resource /Pxxxxx to perform this action: View user permissions on a resource
Any pointers are helpful.

[teerasej]

I have lost the existing token. The person who generated the token first time is no longer with the team. How can I associate a new token from a new account to existing publisher?
I tried creating a token from new account and it says:
ERROR Access Denied: abcxyzteam needs the following permission(s) on the resource /Pxxxxx to perform this action: View user permissions on a resource
Any pointers are helpful.

Got the same thing. I tried to find that permission in the token list, but unlucky.

[swyxio]

hey @maintainers pls put this in your error message or make your UI more intuitive.

[lukepighetti]

Please just give us a one click oauth system. I have no clue what my publisher name is. My token isn't working. I can't figure this out. The docs go in a loop. There is no example of what "publisher" is supposed to look like in package.json. I have never in my life seen an auth flow so complicated, even on dev tooling.

[andradei]

At least a video or blog with screenshots would be a good step towards making this process less of a pain. Right now it sucks big time.

[lukepighetti]

It's the next day and I've given up on publishing from the terminal. Guess I'm rocking the Marketplace upload dropzone from here on out.

[wtakayama-chwy]

It worked for me just when I've allowed full access option

[AnishMandal939]

vsce publish
ERROR Specified part does not exist in the package.

Geting error while publishing other all steps works well

[erlangparasu]

@geddski This is the option you're looking for:

All accessible organizations
thanks it works

[wwdok]

Now it should select All accessible organizations:

[bennycode]

Here is how I solved the 401 error in order to publish VS Code extensions using a GitHub Actions workflow:

1. I set "Organiation" to "All accessible organizations" for my Personal Access Token (PAT)
2. I used a custom defined scope of type "Marketplace: Manage"
3. I set the expiry date to the future
4. I created a GitHub Repository secret with the name of VSCE_PAT (as it is the default env variable used when publishing)
5. I created the following workflow commands:

- name: 'Install dependencies'
  run: |
    yarn global add @vscode/vsce
    yarn install
- name: 'Authenticate'
  run: |
    git config --global user.email "${{ secrets.MY_GITHUB_EMAIL }}"
    git config --global user.name "Benny Neugebauer"
- name: 'Publish VS Code extension'
  env:
    VSCE_PAT: ${{ secrets.VSCE_PAT }}
  run: |
    vsce publish patch

I added a "postversion" script to my "package.json" file to push the version update also to my GitHub repository:

"scripts": {
  "postversion": "git push origin main && git push origin --tags"
}

Full version here: https://github.com/bennycode/sort-everything/blob/v1.3.3/.github/workflows/publish-extension.yml

Hope this helps! ✌️