-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't publish package #507
Comments
Did you follow this guide? https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token Pay attention to:
|
Yes. Everything is the same. And I get the same error form vsce and on the marketplace upload website |
cc @prashantvc: Can you provide more insights? |
@Levminer Do you see your publisher name on https://marketplace.visualstudio.com/manage/ (left on the webpage) |
@prashantvc Yes. |
@SaiKanth007 can you take a look at this issue, please? |
@Levminer While generating the PAT token, can you select "All Accessible Organization" and "Full Access" (instead of custom access). Let us know if the you still get the same error ? |
@SaiKanth007 Yes. |
@Levminer Can you please share the publisherName under which you are trying to publish this extension. Also can you please email us your VSID to [email protected] Steps to share VSID:
|
@Levminer Please restrict from sharing VSID's on public github repositories. Also please share the publisherName under which you are publishing the package |
@SaiKanth007 I sent an email. And my publishername is |
In my package.json in the keywords section had a |
I had the same problem and I set a keyword to "#000000" |
This is purely reproducible issue , in your VScode extensions
I stumbled on this, can this 🐞 be fixed ? |
@eaccmk perhaps you should file separate bug for it |
Every time I log in and try
vsce publish
I get this error:ERROR Access Denied: <my account name> needs the following permission(s) on the resource to perform this action: Allows for the creation of BuiltIn extensions.
The text was updated successfully, but these errors were encountered: