Problem with `scheduler/tracing`

🐛 Bug Report

I have started to get an error from ReactNativeRenderer-dev.js.

It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) without also replacing the `scheduler/tracing` module with `scheduler/tracing-profiling`. Your bundler might have a setting for aliasing both modules. Learn more at http://fb.me/react-profiling

<unknown>
    ReactNativeRenderer-dev.js:15147:2
<unknown>
    ReactNativeRenderer-dev.js:16:2
loadModuleImplementation
    require.js:320:4
guardedLoadModule
    require.js:207:11
metroRequire
    require.js:127:6
<unknown>
    ReactNative.js:18:16
loadModuleImplementation
    require.js:320:4
guardedLoadModule
    require.js:207:11
metroRequire
    require.js:127:6

To Reproduce

I have really no idea what caused this. I have tried everything. I’m running only one version of scheduler (as confirmed by yarn.lock). I can’t see anywhere that the profiling schedule would be enabled, looking through the compiled source.

enableSchedulerTracing is set to true in ReactNativeRenderer-dev.js, which causes the invariant to run, and fails. This happens straight away when the application starts. I have seen it before, but it fixed with remove node_modules and re-installing.

I have wiped + reinstalled (after clearing the Yarn cache). Still broken. I am so so lost. I’ve spent about 5 solid hours now trying to fix this.

Expected Behavior

The app doesn’t die when starting.

Environment

  React Native Environment Info:
    System:
      OS: macOS 10.14.1
      CPU: x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
      Memory: 1.10 GB / 32.00 GB
      Shell: 5.5.1 - /usr/local/bin/zsh
    Binaries:
      Node: 10.9.0 - /var/folders/1d/tp8ckm_52hx1xv7zdjqsrw1h0000gn/T/yarn--1551849609863-0.0831478050093859/node
      Yarn: 1.13.0 - /var/folders/1d/tp8ckm_52hx1xv7zdjqsrw1h0000gn/T/yarn--1551849609863-0.0831478050093859/yarn
      npm: 6.2.0 - ~/.nvm/versions/node/v10.9.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        Build Tools: 23.0.1, 23.0.3, 25.0.1, 25.0.3, 26.0.1, 26.0.2, 27.0.3, 28.0.2, 28.0.3
        API Levels: 23, 24, 25, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4907809
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: ^0.58.6 => 0.58.6

[kuzzmi]

I found a problem and a solution.

I use .env file to pass some environment variables. And the problem was that in some cases my NODE_ENV variable was set to production, but Expo was running in development mode.

So basically the solution is to align the bundler and renderer to use the same NODE_ENV mode.

[jigz]

Same here, why has this issue been closed without a solution.

@deecewan I’d like to know as well how you managed to fix it.