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

Remote debugger bug, react-native v 0.50 android #16977

Closed
universalmind303 opened this issue Nov 25, 2017 · 11 comments
Closed

Remote debugger bug, react-native v 0.50 android #16977

universalmind303 opened this issue Nov 25, 2017 · 11 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@universalmind303
Copy link

universalmind303 commented Nov 25, 2017

Is this a bug report?

yes

Environment

Environment:
OS: Linux 4.10
Node: 8.5.0
Yarn: 1.0.1
npm: 5.3.0
Watchman: Not Found
Xcode: N/A

Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.4 => 0.50.4

Browser: Chrome Version 59.0.3071.115 (Official Build) (64-bit)
Target: (Android 8.0)

Steps to Reproduce

react-native init AwesomeProject
cd AwesomeProject
react-native run-android
enable remote debugger on device

open browser to http://localhost:8081/debugger-ui/

Expected Behavior

device should connect to remote debugger with no errors

Actual Behavior

device will not connect to remote debugger.

console will display -

'Uncaught SyntaxError: Unexpected token ...' localhost/:183

localhost/:183 -
worker.postMessage({
...object,
url: await getBlobUrl(object.url),
});

I reverted back to 0.49 and it got rid of the error, and am able to connect properly, so I am sure it is with 0.50

it looks like the error is coming from object spread operator in /react-native/blob/master/local-cli/server/util/debugger-ui/index.html

Object spread is not supported pre version 60 on google chrome.

Reproducible Demo

react-native init ${app name}

@chmiguel
Copy link

chmiguel commented Dec 1, 2017

i have the same issue on ubuntu 14.04, react native v0.50, on windows the project debugger works fine

@mataoct
Copy link

mataoct commented Dec 7, 2017

i got the same issue on mac

@universalmind303
Copy link
Author

I have a bugfix in my repo, I submitted a PR as well.

You can pull down my version instead of the facebook one

https://github.com/universalmind303/react-native

Another fix ( if you are using chrome ) , upgrade to the latest version of chrome

@MatheusR42
Copy link

Same error here. I update the chrome and now it works.

Thanks @universalmind303

@pedrobertao
Copy link

I've got the error and updating my chrome to the latest version (63) fixed this error.
Thanks @universalmind303

@nsantacruz
Copy link

Started experiencing this error when I upgraded from RN 51 to 52. Just upgraded Chrome from 63 to 64 and still seeing the error 😔

@hjJunior
Copy link

I got the same problem, and I'm using chrome version 64.0.3282.167
Runing react-native: 0.53.3

@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@nsantacruz
Copy link

@react-native-bot, still experiencing this issue on v0.53.0

@anas10
Copy link

anas10 commented Apr 24, 2018

Same here with v0.54.0

@iamtekeste
Copy link

Still seeing this issue with Chrome version 66.0.3359 and React Native version 0.55.4

@facebook facebook locked as resolved and limited conversation to collaborators Feb 24, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

10 participants