malformed message invocationResponse.outputData.data.http.body.object expected

Currently using the v2 Function App version locally to debug on my Mac and it keeps succeed with the following information message and not responding with correct response.

info: Worker.Node.f52ff43c-b7d2-4b78-a3b2-02db6e1302e2[0]
      Worker f52ff43c-b7d2-4b78-a3b2-02db6e1302e2 malformed message invocationResponse.outputData.data.http.body.object expected
info: Worker.Node.f52ff43c-b7d2-4b78-a3b2-02db6e1302e2[0]
      (node:91399) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id:2): invocationResponse.outputData.data.http.body.object expected

I reinstalled azure-functions-core-tools and this info message disappeared, but the function still succeed with a no response.

Upon inspecting the context object, the correct context.res.body data, but when context.done is called context.res changes to null

The function is a GraphQL server, based on the Apollo Azure Functions project (it’s a fork of that as the original project has some problems). This worked for me three weeks ago, but coming back to the project on a fresh install it’s no longer working.

When I upload this to Azure and run it on the v1 runtime (which is where I want it to run in production until v2 is stable) it works perfectly.

Language: NodeJS Version: 8.9.4 Functions tools: azure-functions-core-tools@2.0.1-beta.22

Please let me know if you need anything else. My project repo is private, so I’ll have to create a sanitised version to share if you need it.

[christopheranderson]

@mhoeger is gonna take over on this one. We think we have a solution that is non-breaking that doesn’t force folks to set the raw flag. She’ll describe it in another issue, I think, and link to this.

[christopheranderson]

Notes from repro:

• Modules are in each function folder, can put them at the base of your project and they’ll share dependencies
• When I start it locally on v2 (windows), it returns a 406 status code.
• When I start it locally on v1 (windows), it works!
• When I remove the header, it works on v2 (this is another sign its an issue in the Functions host)
• Given that this is probably our host trying to do too much smarts, I set the “isRaw” flag to true. This worked

    GraphiQL.resolveGraphiQLString(query, options).then(function (graphiqlString) {
        let result = {
            status: 200,
            isRaw: true,
            headers: {
                'content-type': 'text/html',
            },
            body: graphiqlString,
        };
        callback(null,result);

Workaround:

• Set the isRaw flag to true on responses to have our content negotiation stuff turned off.