Bug when decoding Social Google Connection about go-auth0 HOT 4 CLOSED

Hey @alex-restless, we have a fix up for this at #174. I think we might (tentatively) cut a release next week as we'd like to also include some other changes alongside it

from go-auth0.

This issue still persists today, just got bit by it again as I was creating a new tenant and forgot that I originally hit this months ago.

The extra frustrating thing is that if you add a fake value here, and then remove it - the allowed_audiences appears to correctly come through as an empty list. I'm going to keep a fake-value listed in there for now as I know that works, and don't want it to magically rollback to being an empty string and start failing again.

An extra frustrating thing is in the Go SDK it doesn't tell you which field it is that is having troubles.
I had to bypass the SDK and make an HTTP request directly to the endpoint, but then try to marshal the same type. Then I was able to actually view the real issue.

Example:

	url := fmt.Sprintf("%s/api/v2/connections", c.domain)

	req, err := http.NewRequest("GET", url, nil)
	if err != nil {
		return nil, err
	}
	req.Header.Add("authorization", fmt.Sprintf("Bearer %s", accessToken))

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		return nil, err
	}

	defer res.Body.Close()
	body, err := ioutil.ReadAll(res.Body)
	if err != nil {
		return nil, err
	}

	var connectionList []*management.Connection
	err = json.Unmarshal(body, &connectionList)
	if err != nil {
		panic(err)
	}
	return connectionList, nil

Prints the real error:

panic: json: cannot unmarshal string into Go struct field ConnectionOptionsGoogleOAuth2.allowed_audiences of type []string

Where as the SDK prints out a pretty cryptic:

failed to unmarshal response payload: json: cannot unmarshal string into Go struct field ConnectionList.connections of type []string

I'm guessing because it uses a wrapper ConnectionList type to get the pagination data.

from go-auth0.

This hit me again today, any chance of a bump? Appreciate there's a workaround so low priority.

The workaround for me was hinted in the linked issue - I went to the connection, edited the Allowed Mobile Client IDs with a value, then cleared it and hey-presto it works.

go-auth0/auth0#117 (comment)

from go-auth0.

Thank you for fixing this! Upgraded from 0.37.1 to 0.45. Worked like a charm! 🚀

from go-auth0.