Alejandro

Okay so I went to my `.gitconfig` and removed `wincred` and that seems to have possibly done it. I'll keep my eye on it. For what it is worth, I...

> It may be that the stored token had expired, and needed to be refreshed. Reattempting authentication should fix this. That is also what I thought at first, but I...

I'll go ahead and do that - in fact, I'm hitting the 2 hour window since my last commit so I want to see if removing `wincred` did anything. After...

Okay here's what I did, I removed `git-credential-oauth.exe` from the Git directory (I also wanted to test your theory of the 3 credentials being created vs 2). From my Powershell...

I decided to give it a try again, roughly an hour and some after posting my last comment. First time I did `git push`, it failed with the same error....

I was able to replicate the issue - it looks like it deletes the token but did not attempt to refresh it? ``` 18:00:51.813874 ...\Application.cs:106 trace: [RunInternalAsync] Version: 2.3.2.0 18:00:51.813874...

@mjcheetham I can replicate this issue consistently where the credentials gets erased and it re-adds new credentials on `git push`

I come bearing more logs! I haven't performed a `git push` for about ~4 hours but this time it erased the expired token and renewed it? There are about 365...

@ldennington thanks for following up! I have removed `git-credential-oauth` as one of the initial troubleshooting steps but will double check. The problem I am seeing now is that GCM makes...

I am facing the same issue. Are there any updates on this? ``` DEBUG: ============================ HTTP RESPONSE ============================ Status Code: BadRequest Headers: Transfer-Encoding : chunked Vary : Accept-Encoding Strict-Transport-Security :...