No component found for view with name 'RCTVirtualText'

[kevinwchiang]

Description

Updated RN to latest version 0.44. App is crashing on login with the error in the screenshot.

The issue does not occur on Android. I logged out Platform.OS on XCode simulator, and can see that it is logging out ios correctly.

Additional Information

• React Native version: 0.44
• Platform: iOS
• Development Operating System: macOS
• Dev tools: XCode, Simulator

[shahen94]

I'm getting the same error.
Seems like iOS doesn't have this component, so that's ok, but why it's going to require it anyway ?
https://github.com/facebook/react-native/blob/88a63980b58cb4f820229318dba39f0680b76ba3/Libraries/Text/Text.js#L391

[juergengunz]

getting the same error but kinda randomly

[sunkibaek]

I'm getting this error only when I am using https://github.com/CharlesMangwa/react-native-simple-markdown

Any fixes so far? I am getting it when I do a search on a flatlist.

Commented the following in node_modules/react-native/React/Modules/RCTUIManager.m on line 1011

and inserted a return. Things are moving but this needs a fix for sure.

RCTComponentData *componentData = _componentDataByName[viewName];
if (componentData == nil) {
//RCTLogError(@"No component found for view with name "%@"", viewName);
return;
}

[shahen94]

@nickkapoor thatst not a solution.
The problem is that the packager can't find changes in Text.js file due to symlink configuration.

The Solution

1. Open Text.js in your editor.
2. Modify the last lines, for example add logs
3. Save changes
4. Kill packager and run again
5. Open app, probably you'll get error again
6. Reload app, Packager will see changes and will update project

No longer you'll get that error. If you need you can revert your changes in Text.js.
That's all.

Indeed it worked when I put the return. I will undo it and save and re run the packager. Thanks for the guidance.

[cherniv]

Crashes for me even in simple case , like:

render () {
  var a = ['aaa'].map(i => <Text>{i}</Text>)
  return <Text>{a}</Text>
}

[sunkibaek]

@shahen94

Your solution works but that is so weird. Can you explain why it fixes the crash, please?

[shahen94]

@sunkibaek
i though that the packager didn't saw changes, it caches react-native files, i don't know where, but i faced with similar issue 10 months ago. After modifying the file the error disappears. I can't definitely say why it's happening and how packager caches detailed, but i can definitely say that rn packager+watchman had some issues, which can spawn also this issue.

Now you can revert your changes from Text.js, and it will work

[nixoz]

Same here after updated on 0.44
Somehow started work on simulator, but not on device....
iOS

[sunkibaek]

@shahen94 Thanks for the explanation. I've used your tip to fix it on simulator but on device (reelease mode) it shows nothing.

[nixoz]

http://blog.csdn.net/jiangbo_phd/article/details/71482363 - this helped.

npm uninstall react-native-windows
react-native start --reset-cache

I have a component that relies on react-native-windows. node_modules/react-native-windows/Libraries/Components/Button.windows.js'
at Error (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.readFileSync (fs.js:508:33)

So removing react-native-windows does not work. As a side effect of this issue, I am not seeing Text display on the device but shows up on the simulator similar to the issue @nixoz mentioned.