New-GoogleService : Multiple ambiguous overloads found for "AuthorizeAsync"

[sctib]

After going through the initial setup I call Set-PSGSuiteConfig -ConfigName PSGSuite -SetAsDefaultConfig -P12KeyPath $null -ClientSecretsPath "C:\PSGsuite\vocal-facet-xxxxxxxxxxxxxxxx.json" -AppEmail "psgsuite@vocal-facet-xxxxxxxxxx.iam.gserviceaccount.com" -AdminEmail "xxx@xxxxxx.xx" -Domain "xxxxxx.xx" -Preference "Domain" -ServiceAccountClientID "xxxxxxxxxxxxxxxxxxxxxxxx"

It returns with no error

However, subsequent calls gives the error: (get-GSUser).CustomerId New-GoogleService : Multiple ambiguous overloads found for "AuthorizeAsync" and the argument count: "6". At C:\Program Files\WindowsPowerShell\Modules\PSGSuite\2.36.4\PSGSuite.psm1:27207 char:20

• $service = New-GoogleService @serviceParams

• 
  + CategoryInfo          : NotSpecified: (:) [New-GoogleService], MethodException
  + FullyQualifiedErrorId : MethodCountCouldNotFindBest,New-GoogleService

get-GSUser : You cannot call a method on a null-valued expression. At line:1 char:2

• (get-GSUser).CustomerId

• 
  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-GSUser
  **To Reproduce**

Environment (please complete the following information):

• OS: Windows Server 2016
• PowerShell Version: Windows PowerShell 5.1
• PSGSuite Version: latest

[FISHMANPET]

It might be beneficial for us to implement some parameter sets for Set-PSGSuiteConfig, if you're using a Client Secrets Path, you shouldn't specify a P12KeyPath parameter. Without looking at your configuration file, what I suspect is happening is that null value has been saved and then regurgitated into the running config in a way that isn't truly null. When constructing the New-GoogleService, it first checks for a P12Key, and if it finds one in the config it uses that, and if it doesn't find a P12Key it uses the Client Secrets. By specifying P12Key (even as $null) the code is trying to use the nonexistent P12Key instead of trying the ClientSecret you've specified.

Try creating a new config but leaving out P12KeyPath entirely when you create it.