Error: Specified argument was out of the range of valid values. (Parameter 'start')

[andersonbosa]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.89.0 < b58957e67ee1e712cebf466b995adf4c5307b2bd > x64
• OS Version: Ubuntu 24.04 LTS (Noble Numbat)

Steps to Reproduce:

1. Run vsce publish to publish the extension to the store.
2. The previous command will throw the following error: ERROR Specified argument was out of the range of valid values. (Parameter 'start')

2.1. The same behavior occurs when the processor is done by the page: https://marketplace.visualstudio.com/manage/publishers/andersonbosa

[vscodenpa]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[benibenj]

@andersonbosa What version of vsce are you using? And are you using @vscode/vsce instead of vsce (depricated)?

[andersonbosa]

@benibenj Thank you for helping 🙏

I was using vsce 2.15.0. After that, I installed @vscode/vsce (in version 2.26.1) and redid the process. The same error mentioned occurred (evidence in the video below). After that I tried using the --packagePath (because the packaging process is OK) and get same error

 INFO  Publishing 'andersonbosa.commitay v1.0.0'...
 ERROR  Specified argument was out of the range of valid values. (Parameter 'start')

Evidences

source-code: https://github.com/andersonbosa/vsc_extension_commitay/blob/main/commitay/README.md

VIDEOS

with.vsce2_26_1.publish.mp4

with.vsce.2_26_1.publish.with.packagePath.mp4

with.vsce.2_26_1.only.packing.mp4

[benibenj]

Checkout this thread about the same issue you have. It seems like you might be using categories which do not exist
microsoft/vsmarketplace#595

Checkout the available categories here: https://code.visualstudio.com/api/references/extension-manifest#fields

Maybe vsce should validate the categories and provide a better error message in this case. Created an issue to track that: #1005