React Native "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0" log after react-native update

[panda0603]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

[skip envinfo]

Description

I've just updated from react native version 0.55 to 0.57.

After I start the project,

I keep on getting this log

[20:04:52] ::ffff:(IP address) - - [03/Nov/2018:11:04:52 +0000] "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0"

[20:05:02] ::ffff:(IP address) - - [03/Nov/2018:11:05:02 +0000] "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0"

[20:05:13] ::ffff:(IP address) - - [03/Nov/2018:11:05:13 +0000] "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0"

[20:05:23] ::ffff:(IP address) - - [03/Nov/2018:11:05:23 +0000] "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0"

[20:05:33] ::ffff:(IP address) - - [03/Nov/2018:11:05:33 +0000] "GET /onchange HTTP/1.1" - - "-" "okhttp/3.6.0"

on console.log every 10 seconds. The project works fine though. What is this and why is this outputted on the console log? can i disable it?

p.s. I'm using expo-cli. Could this be expo issue?

[Hermanyo]

I'm face this issue too, when I downgrade to 0.55.4, all works again

[soooji]

Me too. Is there any solution? I hate downgrade.

[aminnoura]

I have the same issue....

[enanda]

same here

[stickyburn]

Looks like something from the update.. Maybe its a watchman issue ? I've been trying to look for a flag to stop these logs but no luck so far..

[clintjansen]

Yea, I believe this is an Expo issue only.
Happens since it updated to SDK 31.0

[Hermanyo]

My project is to react native cli, and I had the same problem

[fantasy525]

same issues,and there are too many Http infos.....

[panda0603]

update your expo-cli to latest version, should fix most of it except the
"POST /symbolicate HTTP/1.1" 200 - "-" "okhttp/3.6.0".

[Hermanyo]

I'm not using expo-cli, I don't have expo in my project, and I face this problem, too... is there any solution? anyone?

[Hermanyo]

UP

[Thimeryan]

I only had this issue when I enabled live-reloading on the emulators. Once turned off the problem went away.

[elicwhite]

Based on @Thimeryan's comment, it sounds like this network request is expected with live reloading.

[mwkthang]

Run command on windows set EXPO_DEBUG=false and the error will be gone.

[muhyidin3222]

sudo lsof -i, and kill your java