Vscode-vsce: `vsce publish` fails with "Error: The category 'Languages' is not available in language 'en-us'."

Created on 1 Apr 2018  路  13Comments  路  Source: microsoft/vscode-vsce

Used vsce publish a week ago with no issues. Yesterday and today, I've tried to push up a new version but it always fails with an error:

Error: The category 'Languages' is not available in language 'en-us'.

The only change I made to package.json was to update my version from 0.1.0 to 0.1.1. The categories field is currently set to:

"categories": [
    "Languages"
],

Using vsce 1.37.6

Most helpful comment

Appears to be working again, must have been a server side issue.

All 13 comments

I am experiencing the exact same issue. I was able to publish a day or two ago, but haven't been able to this morning with that exact error.

I get the same error both using vsce publish and the web-based VSIX upload.

Same for me

Currently blocked on publishing because of this, at https://github.com/alanz/vscode-hie-server/blob/master/package.json#L26.

Appears to be working again, must have been a server side issue.

cc @viradhamMS @pkuma-msft

Yes, this was an issue on Marketplace's side. We disabled the feature flag for mitigation. We are working on a fix..

Fails for me too currently 馃槨

@jrrdnx , @mike-lischke : Meanwhile, if you can use the category "Programming Languages", it will unblock your publish. Can you please try this?

BTW, the issue is fixed now. you can use either of the categories. I suggest to use the new one going forward - "Programming Languages"

The problem with that is that my extension now fails to activate. I had to return to languages to make it work again.

Hi @mike-lischke could you please elaborate on the failure you're seeing? We tried forking your repository, changing category to Programming Languages, building the extension with vsce and installing it on VSCode. The syntax highlighting and error checking worked for antlr files.

Is it possible for you to install the 2.0.1 release of my extension from the marketplace? Meanwhile I updated that to make it work again. I'm using vscode 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1).

What I saw was that after updating the extension in vscode I got a message for my .g4 files saying that there are extensions in the marketplace that could handle such files. And none of the extension features worked. Most obviously the syntax highlighting was different, also symbol lookup didn't show anything. This told me enough, since the only change I made was that language setting. So I reverted that and published an update, to avoid frustration for my users.

Hi @mike-lischke , we checked the 2.0.1 release of your extension and that has category Languages and not Programming Languages (categories are same in 2.0.1 and 2.0.2). Also, the verison 2.0.1 isn't giving syntax highlighting as you said. Would it be possible due to the other changes/updates present in version 2.0.1? Could you please mail us at [email protected] and we'll share with you the 2.0.1 release.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

joaomoreno picture joaomoreno  路  4Comments

jkeech picture jkeech  路  4Comments

brandoncc picture brandoncc  路  6Comments

usernamehw picture usernamehw  路  4Comments

shanalikhan picture shanalikhan  路  6Comments