Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[email protected]' could not be found #13731

Closed
Sir-hennihau opened this issue May 2, 2017 · 3 comments
Closed

[email protected]' could not be found #13731

Sir-hennihau opened this issue May 2, 2017 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@Sir-hennihau
Copy link

Sir-hennihau commented May 2, 2017

Code worked yesterday, but today not anymore. Didn't change a thing. This occured to me multiple times.

I get the following error. Couldnt reliably fix it yet.

error: bundling: Error: 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets/[email protected]' could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13
Bundling index.android.js 100.0% (432/432), failed.
Error: 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets/[email protected]' could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13
Error: 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets/[email protected]' could not be found, because 'node_modules/react-native/Libraries/CustomComponents/NavigationExperimental/assets' is not a subdirectory of any of the roots ('/home/sirhennihau/Workspace/next')
at /home/sirhennihau/Workspace/next/node_modules/react-native/packager/src/AssetServer/index.js:181:13

I run code for a static userinterface mockup. Uses compressed media data in the views.

"dependencies": {
"react": "16.0.0-alpha.6",
"react-native": "0.43.3",
"react-native-video": "^1.0.0"
}
Run on an Android
Ubuntu 15
Atom, Android SDK, node.js, React-Native-Video.

Any suggestions?


 render() {
    return (
      <ScrollView>
        <Text>RnB</Text>
        <ScrollView horizontal={true}>

          <Video
          style={{ flex: 1 }}
          source={require('./app/media/compressed/Chrisbrown-1.mp4')}
          style={{ width: 150, height: 150 }}
          ref={(ref) => {
            this.player = ref
          }}
          muted={true} />

          <Video
          style={{ flex: 1 }}
          source={require('./app/media/compressed/Freestylekendrick-1.mp4')}
          style={{ width: 150, height: 150 }}
          ref={(ref) => {
            this.player = ref
          }}
          muted={true} />
          ...
        {/*
        //Multiple ScrollViews follow here, containing videos and images
        */}
          ...`


@saubcy
Copy link

saubcy commented May 5, 2017

you can set a long REACT_NATIVE_FSOP_TIMEOUT, the default value is 15000ms, but if toooooo mutch files if may not enough, but it give a confused error msg...
btw, you can change it in /node_modules/react-native/packager/src/AssetServer/index.js

@achuvm
Copy link

achuvm commented Jul 12, 2017

Thanks @saubcy! This solved the issue for us because we have ~600MB of assets in the packager.

@hramos
Copy link
Contributor

hramos commented Sep 21, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Sep 21, 2017
@hramos hramos closed this as completed Sep 21, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Sep 21, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Sep 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants