Invalid content type, expected application/json, parseJsonBody.js, symbolicate endpoint

[mlassauzay-pass]

Hi !

I just bumped RN from 0.78 to 0.80 and I'm getting this error message triggered in my code when I change screens.

Error: Invalid content type, expected application/json
    at .../node_modules/metro/src/lib/parseJsonBody.js:11:16
   ...

A request is made to the symbolicate endpoint, which attempts to parse the request via parseJsonBody.
parseJsonBody has been modified between 0.78 and 0.80 and only accepts requests with req.headers["content-type"] which contains application/json, but in my case the request it receives contains "text/plain", so it displays this error message. The request content does indeed appear to be JSON, and if I comment out the header validation, the request seems to be processed correctly and I no longer get an error message.

The request trace points to a call to navigate in my code, but I have no further information and navigation works correctly. I tested this with react-navigation 6 and 7.

I'm wondering if anyone else is familiar with this problem, which is causing a lot of error message on the my console ?
I haven't been able to determine if it's a problem with one of my libraries or if parseJsonBody could simply be more permissive.

[robhogan]

Hi @mlassauzay-pass, thanks for the report. If the header constraint is new that might be an unintentional breaking change we could relax (although as you say the content must be JSON in any case).

It’d be interesting to know where the request to /symbolicate is coming from, since this isn’t a problem we’ve heard about iirc. Is this vanilla/community RN? Do you have anything installed that might be doing its own error handling (sentry or similar?)

[robhogan]

Looks like the change was in #1475 and I did spot the breaking change in (internal) review but it slipped through anyway.

If you want to put in a PR to update the call to parseJsonBody on /symbolicate to use strict: false, I’d be happy to accept that.

[mlassauzay-pass]

Thanks for your answer @robhogan.

Unfortunately I can't get any more information about the request send to symbolicate/. I know the trace sent refer to a navigate in my code, but I have no idea exactly what triggers the request and why.

I'm not sure that answers the question but the project doesn't use expo, we use directly react-native": "0.80.2" in package.json and @react-native-community/cli is in devDependencies.
We use Sentry but it is disabled in __DEV__ so I don't think comes from there.

I will propose a PR for the strict as soon as I have a moment, even though I think that it may not be the ideal solution, and I leave it to you to decide.

[mlassauzay-pass]

@robhogan I opened a PR with my other github account