Closed pierrediancourt closed 7 months ago
@pierrediancourt huh. I have the exact same PS version and run 'Get-GOAuthTokenService' on a regular basis. Our production automation servers when we created that were 5.x
Alright, fair enough :D That's probably an issue caused by something else then. I'll be glad to update the title of this issue with truer label if we get to the bottom of this mystery !
the actual issue is the system locale / culture settings see https://stackoverflow.com/a/66022792
Alright, fair enough :D That's probably an issue caused by something else then. I'll be glad to update the title of this issue with truer label if we get to the bottom of this mystery !
Hi! I encountered this issue couple days ago when i've changed date format from MM/dd/yyyy to dd.MM.yyyy in my OS settings. After that my code similar to above mentioned ceased to work in powershell 5.1 but was still okay when running in PowerShell 7.2.1. Ultimately i reverted changes with date format back and code was working in powershell 5.1 again Don't know if it's related to this case but i hope this is gonna help "to get to the bottom of this mystery" in a way :D
Item closed as of module 2.0.2 -> pulled in Ronny's update as the fix. All code tested in Ubuntu LTS 22 and Windows 11 (pwsh 7.4 / powerShell 5.1)
Hello,
When running this basic code made of the Example.ps1 file provided in this repo
I get this error
But only when i run it in powershell 5.1
There's no error thrown and the token is displayed when running in PowerShell 7.2.1
My clock is synced with microsoft time servers as it is the default on any W10 machine. I can live with running that with the pwsh binary but i thought it should be referenced somewhere :)
Thanks for your work on that project