search

edgafner / dorkag

Issue Tracker repository for all Dorkag plugins
Other
5 stars 0 forks source link

[BUG]: Account already exist #71

Closed olegpoltora closed 6 months ago

olegpoltora commented 6 months ago

Describe the bug Each several weeks this plugin loose authorization. Existed token can't pass authorization. New token can't pass authorization.

And again, after your answer at plugin page, plugin again loses authorization, and again it's impossible to use existed token.

New token also can't pass. Error: Account [my-email@my-company] already exist.

I already have several tokens at AzureDevOps personal access token's page. image

After removing user in 'Version control -> AzureDevOps' my token passed and I got authorization.

Desktop:

JetBrains IDE:

Jonatha1983 commented 6 months ago

Hi @olegpoltora

I really want to find the root cause of this issue you are having. Even though tens of unique users use the plugin every day, you are the only one who reports this issue, but I honestly want to help.

I do have two requests for you:

  1. You are responsive; compared to your other opened issues, it would be great if you could reply after I work hard to try to fix and help you. You don't need to respond immediately or even in the same week, but it will be nice to have a small response to the previous one before opening a new issue.
  2. Please remove the bad review submitted on the plugin page. I am working hard to support users' issues, including yours, and I don't see any good reason why, after trying to help you and others here, someone would publicly post an evil review as you did.

Now about the issue:

Can you check those:

  1. When you create a PAT in Azure DevOps, you need to set the expiration date. Are you sure the tokens you created didn't expire?
  2. When you go to your IDE settings under Appearance & Behaviours > System Settings > Passwords, what is your selection? (The plugin uses the infrastructure Jetbrains code to deal with passwords and tokens. )

If both of those didn't work - can you try to create a completely clean local rep? If so, try working on that with the plugin and see if the issue persists.

Again, I would really appreciate it if you could update here about it, especially because if there are other users suffering from this, they will know.

Thanks