I am currently trying to upgrade our application to Expo SDK v32.0.0, however running the app in a simulator immediately after loading with expo start -c, I immediately get:
“There was a problem sending log messages to your development environment”, which I am able to dismiss, but will immediately reappear on subsequent calls to console.log, etc. anywhere in the application. I ran expo diagnostics and get the following:
Update - I was able to find a solution for this issue. It is a bug that appears for me when redux-logger is used in the application. Specifically, if I intercept actions that include a request/response payload, I was able to squash or recreate the error. I was able to squash the error by removing the request property from action.payload in the redux-logger (using lodash/omit):
I got this error consistently when dumping the result of an axios call to console like console.log(result). Once I used console.log(JSON.stringify(result)) the problem went away. I imagine it has something to do with escaping.
I updated to v32 and things are working, however I did get this error showing up later due to a seemingly unrelated bug in my own code
I’m using graphQL, and was accidentally trying to pass a variable in a query that wasn’t defined in my schema, which oddly enough was throwing this same error.
Yes, I am also facing the same issue with expo sdk 32.0.0 and axios. Also as gerbus mentioned, with JSON.stringify the error disappears. I think expo cannot handle large data to send on the console. And so I don’t think this has been resolved in expo sdk 32.0.0. Would be great if this gets fixed soon.
Had same issue with expo SDK 32.0.0 while using console.log(response) in axios. As mentioned by @gerbus and @kakarnconsole.log(JSON.stringify(response)) fixed it.
I’m also running into this issue. I can’t tell where it is coming from. It appears to be some code in a library that I don’t control using console.log. Highly annoying!