Possible encoding error in New-AppSourceSubmission

[jonaswre]

I was just trying to get New-AppSourceSubmission to work.

But it seems like there is an Issure with the encoding when posting or putting content.

First error I recieved was in.

navcontainerhelper/AppSource/New-AppSourceSubmission.ps1

Line 151 in 7d5fbb4

$packageUpload = Invoke-IngestionApiPost -authContext $authContext -path "/products/$productId/packages" -Body $body -silent:($silent.IsPresent)

If the filename has any special characters (äöü) then the request fails with internal server error (500).
There is an easy workaround. I just renamed the file.

But for the second problem there is no easy workaround.

The following line "reuploads" the terms and services which need to have special characters.

navcontainerhelper/AppSource/New-AppSourceSubmission.ps1

Line 221 in 7d5fbb4

$result = Invoke-IngestionApiPut -authContext $authContext -path "/products/$productId/properties/$($property.id)" -Body ($property | ConvertTo-HashTable -recurse) -silent:($silent.IsPresent)

Just because was curious i edited the terms and services to "Test".

That "fixed" it.

Just as a note the terms were correctly printed in the log which could mean the get works fine.

[freddydk]

Will investigate, thanks Jonas

[freddydk]

This is apparently a bug in PowerShell - if your body contains UTF-8 characters - you cannot transfer a json string - you need to transfer a byte[]

[jonaswre]

It seems like json and powershell are arch rivals. Thanks for the fix.

[freddydk]

Shipped in 4.0.3