tfx extension publish - fails to detect existing extension

After having sidestepped this issue for two days or so and publishing through the web gui I decided to have another go at publishing an extension from the command line. But the best I can get is:

tfx extension publish --token xxx --rev-version
TFS Cross Platform Command Line Interface v0.3.37
Copyright Microsoft Corporation
Checking if this extension is already published
It isn't, create a new extension.
Failed Request: Conflict(409) - The extension already exists.

I am pretty sure that the extension cannot both be published and not. I am also using --rev-version option and it is creating new .vsix files that I can publish from gui.

I am using visual studio online and it does not seem to help to:

• use v0.3.37 instead of v0.3.30 from npm
• create a new extension
• fiddle around with the authentication token
• try to provide a service-url

Would be grateful for any suggestion how to get past or diagnose this.

[willsmythe]

99% of the time, this message means the identity associated with the PAT does not have access to the extension that has already been published to the Marketplace(which is why the message says “It isn’t [published yet”]). This can happen if you sign in and publish the extension under one VSTS identity, but then create and try to use a PAT associated to a different VSTS identity

I think we should improve the message here to call this out better since this isn’t obvious today.

[xximjasonxx]

I figured this out. My Microsoft Identity was a complete mess and I had to delete a bunch of extraneous directories and “move” my Azure DevOps org to my default tenant