Storage Explorer Version:
1.0.0
OS Version:
Platform: macOS
Architecture: x64
Build Number: 20180415.2
Commit: 5d603052
Support Id: ca79a3ff-0016-7bd0-8f06-ea5fa1529f0b
Steps to Reproduce:

Expected Experience:
The second account credentials must be updated.
Actual Experience:
The second account credentials are outdated...
1.0.0 introduced a new component for managing sign-in credentials. Can you try signing out of your accounts then signing back in?
@vladbilyk , are you also using VS for Mac?
@craxal removing account and adding it back works fine... but I believe that second account was added on 1.0.0 version, anyway if the issue comes again I will inform you...
@MRayermannMSFT yep, I'm using VS for Mac
Awesome. If you encounter it again, we can reopen and investigate.
@vladbilyk , let me know if you run into the issue again. I know the cause and I know how to get you out of it. Thanks!
I have just run into the issue with an Azure AD account.
Unable to sign-in: Duplicate query parameter 'prompt' in extraQueryParameters
Version: 1.0.0
Platform: macOS
Architecture: x64
Build Number: 20180415.2
Commit: 5d603052
Support Id: cc1e9539-7af3-8377-627c-36d500960dc9
Hi @mcetkovsky , do you have a ~/.IdentityService/aadconfiguration directory (my casing of the directories may be wrong)?
Yes, I do. I have just a single file Inside the directory, called AadConfiguration.lock.
Hmmm that's odd. There should have been a configuration in there. Can you do following?
I've removed names, e-mails, some tennant ids and logos.
IdentityService 2-1.zip
Yep, ok, looks like at one point you did have an Aad Configuration that you used to add that account to VS for Mac. Simply remove the account using either Stg Exp or VS for Mac, and then re-add it using Storage Explorer. You should be able to use the account that is then added in both Stg Exp and VS for Mac.
That worked. However, the solution is not very self-discoverable :)
Definitely not discoverable. I've added it to our known issues for the next set of release notes, so hopefully people see that. Our auth team is also working on a fix so this situation doesn't happen in the future. 馃槂
Most helpful comment
Definitely not discoverable. I've added it to our known issues for the next set of release notes, so hopefully people see that. Our auth team is also working on a fix so this situation doesn't happen in the future. 馃槂