Cannot read property 'BLOB_URI_SCHEME' of undefined after upgrade to RN48

[rknell]

• Jest v21.0.1
• I have removed and reinstalled the node_modules folder
• I have run jest --no-cache

Node version: 7.8.0

Also used NVM to upgrade to Node v8.4.0, fresh yarn global install, deleted node modules and reinstalled, error still exists.

{
	"name": "rnJestBugRepl",
	"version": "0.0.1",
	"private": true,
	"scripts": {
		"start": "node node_modules/react-native/local-cli/cli.js start",
		"test": "jest"
	},
	"dependencies": {
		"react": "16.0.0-alpha.12",
		"react-native": "0.48.1"
	},
	"devDependencies": {
		"babel-jest": "21.0.0",
		"babel-preset-react-native": "3.0.2",
		"jest": "21.0.1",
		"react-test-renderer": "16.0.0-alpha.12"
	},
	"jest": {
		"preset": "react-native"
	}
}

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Fresh project, RN0.48.1 fails with error running yarn test. I noticed the error appear on an existing project after upgrading to RN0.48.1 on every test.

TypeError: Cannot read property 'BLOB_URI_SCHEME' of undefined
      
      at Object.<anonymous> (node_modules/react-native/Libraries/Blob/URL.js:21:21)
      at node_modules/react-native/Libraries/Core/InitializeCore.js:174:40
      at getValue (node_modules/react-native/Libraries/Utilities/defineLazyObjectProperty.js:44:10)
      at ContextifyScript.Script.runInContext (vm.js:32:29)

Commenting out the blob requirement in the node_modules/react-native/Libraries/Blob/URL.js:21:21 file allows the app to continue to pass all tests. The app runs without errors with no source code modification.

I have a copy of my code here: https://github.com/rknell/rn0481JestBugReproduction

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.

What is the expected behavior?

Tests continue to run as normal

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

Please see repo for config, further details below

Npm (on node 8 5.3.0)
Yarn 0.27.5

[cpojer]

This seems like a change needs to be made in react-native, not in Jest.

[thymikee]

Yup, this is bug in react native, fixed in master while updating flow version so its not yet in the release channel.

[rknell]

I was of two minds where to put it, but decided to put it with jest as react native is working fine and as expected, so it feels as though the JavaScript environment isn't being spin up correctly for react native testing. I understand Jest is supposed to be react and react native independent, but I didn't see the react native team changing their stack to make it jest compatible if it's building and running properly. I will raise an issue with them

…

On 6 Sep. 2017 7:33 pm, "Christoph Nakazawa" ***@***.***> wrote: Closed #4433 <#4433>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4433 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFmlbfWjNIrV5wBh5y69B850YMACNvoTks5sfmb9gaJpZM4PNsvz> .

[rknell]

Ahh just saw the new response. Thanks Michael, so the fix is a couple of months away then?

…

On 6 Sep. 2017 7:40 pm, "Ryan Knell" ***@***.***> wrote: I was of two minds where to put it, but decided to put it with jest as react native is working fine and as expected, so it feels as though the JavaScript environment isn't being spin up correctly for react native testing. I understand Jest is supposed to be react and react native independent, but I didn't see the react native team changing their stack to make it jest compatible if it's building and running properly. I will raise an issue with them On 6 Sep. 2017 7:33 pm, "Christoph Nakazawa" ***@***.***> wrote: > Closed #4433 <#4433>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#4433 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AFmlbfWjNIrV5wBh5y69B850YMACNvoTks5sfmb9gaJpZM4PNsvz> > . >

[rknell]

To anyone coming across this, facebook/react-native#15810 is the relevant issue, and you can avoid the issue for now by rolling back to node v7.4.0

[SaraChicaD]

Thanks for that @rknell ! Fixed my issue, appreciate you!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.