You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a simple graphql which returns Unsupported Content-Type header, use application/json 2025-01 error in 2025-01 although it works fine versions <= 2024-10.
{
productVariantsCount {
count
precision
}
}
It works fine when we add an empty object as variable to the graphql to force json usage here:
JSON body support: We now provide native support of a HTTP request body as a JSON_body for function external calls. Use this field when the body is in JSON format to reduce function instruction consumption and to ensure the body is formatted in logs. Don't use the JSON_body field together with the body field in the HttpResponse object. If both are provided, then the HttpResponse's body field takes precedence. If the JSON_body field is specified and no Content-Type header is included, then the header will automatically be set to application/json.
The text was updated successfully, but these errors were encountered:
I have a simple graphql which returns
Unsupported Content-Type header, use application/json 2025-01
error in 2025-01 although it works fine versions <= 2024-10.It works fine when we add an empty object as variable to the graphql to force json usage here:
Related changelog:
https://shopify.dev/docs/api/release-notes/2025-01
JSON body support: We now provide native support of a HTTP request body as a JSON_body for function external calls. Use this field when the body is in JSON format to reduce function instruction consumption and to ensure the body is formatted in logs. Don't use the JSON_body field together with the body field in the HttpResponse object. If both are provided, then the HttpResponse's body field takes precedence. If the JSON_body field is specified and no Content-Type header is included, then the header will automatically be set to application/json.
The text was updated successfully, but these errors were encountered: