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

You cannot render into anything but a top root #14717

Closed
Symous opened this issue Jun 24, 2017 · 19 comments
Closed

You cannot render into anything but a top root #14717

Symous opened this issue Jun 24, 2017 · 19 comments
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@Symous
Copy link

Symous commented Jun 24, 2017

Description

I have met this error irregularly after I update RN to 0.45.1

Reproduction Steps

Modify any code of the program and "Reload".

Solution

Just reload again and the error will disappear.

Additional Information

  • React Native version:0.45.1
  • Platform: Android
  • Development Operating System: Windows 10 64 bit
@kmiloarguello
Copy link

Thank you!

@poupryc
Copy link

poupryc commented Jun 25, 2017

Hello,

I'm on 0.46.0-rc.2, using Ignite-CLI and boiterplate.
This error doesn't disappear when I reload my app...

Additional Information

Platform: Android
Development Operating System: Windows 10 64 bit

@Symous
Copy link
Author

Symous commented Jun 26, 2017

@kmiloarguello Hi,guy. I do not know the reason why this error occured.Is it a bug of RN and Is there any way to solve this for good?

@jetzhliu
Copy link
Contributor

I have met this error in RN 0.46-rc2 on Android emulator and real machine.
But when I downgrade RN to 0.45.1, this error disappears.

@poupryc
Copy link

poupryc commented Jun 27, 2017

Thank, I will try later

@kmiloarguello
Copy link

@Symous I thought it would be an Android emulator error maybe when React Native builds the package but really I don't know... Actually I get this error sometimes but I just reloading again solve the problem.

@poupryc
Copy link

poupryc commented Jun 27, 2017

I get this error on physical device (O+ 3T 7.1.1)

@fredbt
Copy link

fredbt commented Jun 30, 2017

I get this error when react-native packager dies (see #12895).

@yash2code
Copy link

same issue

@ecasona
Copy link

ecasona commented Jul 5, 2017

I have got this error for more times in RN 0.45.1 when I reload my project,but try again ,it solved.

@ricbermo
Copy link

ricbermo commented Jul 5, 2017

I'm using Expo SDK 18, which is based on NR 0.45 and for me the only way to workaround this issue is to open remote debugger

@mrfzd
Copy link

mrfzd commented Jul 7, 2017

Same issue here, after React Native 0.46 was released yesterday I downloaded and configured everything to what React Native suggests, Node v6.11 and downgraded npm from 5 to 4
Download Expo and opened emulator, started the app and in the Expo clicked on Device

Everything works but this error intermittently occurs and it's very annoying!
Hope they fix this annoyable bug ASAP

@mrfzd
Copy link

mrfzd commented Jul 7, 2017

As of today 7th July, the best way round this problem is to enable "Ctrl + M > Remote JS Debugger" from your emulator
Hope it helps

@nimabk82
Copy link

I get this error (real device) when I try to dismiss a modal and I have to say I'm using react-native-navigation lightbox

  <TouchableOpacity style={{alignSelf: 'flex-end',}} activeOpacity={0.6} onPress={this.props.navigator.dismissLightBox.bind(this)}>
                    <Text style={{ padding: 16, color: 'orange'}}>CANCEL</Text>
</TouchableOpacity>
 

@lipingruan
Copy link

@nimamyscreen

wix/react-native-navigation#1502

@hemedani
Copy link

hemedani commented Aug 30, 2017

this hackThis hacky by @rawrmaan fixed for me
change the destroy method on node_modules/react-native-navigation/android/app/src/main/java/com/reactnativenavigation/views/LightBox.java

    public void destroy() {
        // content.unmountReactView();
        dismiss();
    }

tank you man

@christoshrousis
Copy link

Above fix doesn't resolve for me on

"react-native": "0.46.4",
"react-native-navigation": "^1.1.230",

@hemedani
Copy link

@christoshrousis you should reinstall app on devices

thanhzusu pushed a commit to thanhzusu/react-native-navigation that referenced this issue Oct 5, 2017
thanhzusu pushed a commit to thanhzusu/react-native-navigation that referenced this issue Oct 5, 2017
jiabinxu added a commit to jiabinxu/react-native-navigation that referenced this issue Nov 22, 2017
@stale
Copy link

stale bot commented Nov 26, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Nov 26, 2017
@stale stale bot closed this as completed Dec 3, 2017
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests