`Content type application/json does not have a factory registered to be parsed`

[hognevevle]

Following an upgrade to 1.16.0, I recently upgraded my app dependencies as instructed by Kiota.

Previous dependencies in package.json:

    "@microsoft/kiota-abstractions": "1.0.0-preview.56",
    "@microsoft/kiota-http-fetchlibrary": "1.0.0-preview.55",
    "@microsoft/kiota-serialization-form": "1.0.0-preview.45",
    "@microsoft/kiota-serialization-json": "1.0.0-preview.56",
    "@microsoft/kiota-serialization-multipart": "1.0.0-preview.34",
    "@microsoft/kiota-serialization-text": "1.0.0-preview.53",

New dependencies in package.json:

    "@microsoft/kiota-abstractions": "1.0.0-preview.57",
    "@microsoft/kiota-http-fetchlibrary": "1.0.0-preview.56",
    "@microsoft/kiota-serialization-form": "1.0.0-preview.46",
    "@microsoft/kiota-serialization-json": "1.0.0-preview.57",
    "@microsoft/kiota-serialization-multipart": "1.0.0-preview.35",
    "@microsoft/kiota-serialization-text": "1.0.0-preview.54",

Unfortunately, I'm getting the following error after installing the new versions with yarn

Error: Content type application/json does not have a factory registered to be parsed
    at ParseNodeFactoryRegistry.getRootParseNode (parseNodeFactoryRegistry.ts:38:9)
    at fetchRequestAdapter.ts:374:34
    at async fetchRequestAdapter.ts:188:24
    at async fetchRequestAdapter.ts:166:12
    at async Proxy.init (cart.ts:75:24)

Tried deleting node_modules and reinstalling everything, to no avail.

Rolling back to the previous dependency versions does however fix the problem.

[hognevevle]

Possibly a duplicate of #1244. Close at will, or let me know if there's additional details I can provide.

[andrueastman]

Thanks for raising this @hognevevle

Any chance you can confirm the workaround provided at https://github.com/microsoft/kiota-typescript/issues/1244 works out for you? If so we can close this so that this can be followed up in that issue....

[hognevevle]

Hi @andrueastman , I don't use the Kiota CLI though -- only the VSCode extension. Is there a way to achieve the equivalent of --serializer none --deserializer none from the extension? If so I could try that.

[baywet]

@hognevevle in the extension it's a setting at this point.

[nreinartz]

The workaround seems to work, although you don't need to re-generate the kiota client without the serializers. Simply passing a custom parseNodeFactory (as shown in the example of #1244) to an existing client works.