[0.73] Remote JS Debugging deprecation #734
Replies: 3 comments 5 replies
-
|
I welcome this change very much! Many developers I interacted with didn't even realize that "remote debugging" is running V8 instead of the device's JS engine (I guess the notion of a "JS engine" is also foreign to many developers). And they only learned the difference after bumping into a date issue between JSC and V8 to something of that sort |
Beta Was this translation helpful? Give feedback.
-
|
I agree; I think the new RN JS Inspector will be a much better DX than the remote JS Debugger. But -- I did appreciate having the Remote JS Debugger as an option. It did help me solve some things in the past! Just time for it to go I think. |
Beta Was this translation helpful? Give feedback.
-
|
It's great that the future debugging experience looks bright. But deprecating the remote debugging has caused a lot of pain. There are posts all over from folks having no way to use the classic redux-devtools and react-native debugger. Yes, I am aware remote debugging can be turned back on manually, but then there are bugs blocking people from doing so. The fixes may be "easy", but clearly not easy enough because I just joined a team of 30 RN devs who didn't even realize it was still available. And also... for such critically important functionality, its confounding that we have to use patch package to get it working again (re async Hermes error). The experimental debugger has not been an acceptable substitute. I have a little logger that pretty prints colored objects. I've been using it for years in chrome console. It won't work because the experimental debugger has a bug that prevents pretty printing JSON.stringified objects. So in addition to there being major functionality missing, like network calls, it still struggles with a basic console.log. And Flipper was not a good choice for a hold-me-over, considering it's deprecated too and the reasons for which it is deprecated. I am happy to see it go... except what the heck? What are we supposed to use? Reactotron? Redux devtools and react-native-debugger are insanely useful. Maybe not as pretty as the competition, but something many of us relied on heavily because it just does what it does perfectly. It is without equal. To have that taken away, we feel we have been left hanging... It really is surprising too, when I think of how many major commercial decisions must have been made to go with redux because of those devtools. My point in saying all this is not to offend anyone. If anything, I am appreciative of the opportunities RN has provided me in my career. But it is to say I think the impact of deprecation has been greatly underestimated and it would be really unfortunate if remote debugging was taken out a second before it absolutely has to be. If anything, it should be restored to previous health until the new tooling is mature. It doesn't seem like much work would be required to do so. |
Beta Was this translation helpful? Give feedback.
-
|
@jehillert Thanks for your input. Two immediate things (in lieu of a longer reply I will locate on the feedback thread):
If you have any more feedback, consider adding to this reply and I'll try to respond and share future updates from the team 🙏🏻. |
Beta Was this translation helpful? Give feedback.
-
This is good to hear. The official RN documentation just says it "will be removed in a future release". |
Beta Was this translation helpful? Give feedback.
-
|
Btw, it was 4:00 AM when I wrote that. The reality is I make all my money using the technology you guys created. Me and half a million other developers. I'm appreciative. |
Beta Was this translation helpful? Give feedback.
-
|
While I have your attention, there is one specific thing that lead me to post in the first place. It's that react-native-debugger is broken. It's pretty much the best tool I've seen. Or it works, but then there's this error: I was able to fix it in the past with no problems, with this fix: It's not just discussed on github. Other people have been running into it and posting on reddit and stack overflow. I used to be able to fix it, but now it doesn't work anymore. I can use react-native-devsettings to get the debugger to work, but the patch is needed to suppress the error, and the app crashes if you don't leave it in remotedebugging mode. As far as I can tell, whatever atob was supposed to do it doesn't do anymore. Could be wrong, but I think even expo devtools is running into it in some cases. Maybe tons of people just use rnd, but it seems to be a widespread problem. I know this isn't the place to mention this normally. But this error has been around for almost a year, the solution so far has been a patch, and now the solution is broken. The debugger is a really big deal for daily development. It would help if there was more attention on just gettting our old tooling back. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I am a beginner in React Native and currently developing an app with it. I heard that the remote debugger is being deprecated, so I tried to check for memory leaks using the Xcode Instruments Leaks template, but encountered an issue. My development environment includes: React Native version 0.74.2 (without the new architecture) ===== import React, {useEffect, useState} from 'react';
import {StyleSheet, View, Text, TouchableOpacity} from 'react-native';
export interface MemLeakProps {
/** debug mode */
isDebug?: boolean;
}
export const MemLeakSetInterval: React.FC<MemLeakProps> = ({
isDebug = false,
}) => {
if (isDebug) {
console.log();
console.log('<===MemLeak===>');
console.log();
}
const [count, setCount] = useState(0);
console.log('now count:', count);
useEffect(() => {
console.log('+++ MemLeak mount!');
const intervalId = setInterval(() => {
setCount(prevCount => prevCount + 1);
}, 1000);
return () => {
console.log('--- MemLeak unmount!');
};
}, []);
const handleButtonClick = () => {
console.log('button touched!!');
};
return (
<View>
<Text>{count}</Text>
<Text>Memory leak component</Text>
<View style={{marginTop: 15}}>
<TouchableOpacity onPress={handleButtonClick}>
<Text>Click me</Text>
</TouchableOpacity>
</View>
</View>
);
};
const styles = StyleSheet.create({
container: {width: '100%', flexDirection: 'row'},
});==================== Is this behavior normal? Could you provide a simple example code to test if memory leaks are correctly detected in Xcode Instruments? Additionally, what is the appropriate debugging method to accurately find and trace the location of intentional memory leaks in a React Native memory leak example? Thank you. |
Beta Was this translation helpful? Give feedback.
-
Introduction
In React Native 0.73, we are deprecating Remote JavaScript Debugging via Chrome (docs).
Remote JavaScript Debugging was previously the default debugging experience for apps using JavaScriptCore (JSC). It involves switching JavaScript execution into an external V8 process, to debug in the Chrome browser.
Motivation
We are focusing future debugging efforts into providing a first-class experience for Hermes.
Alternatives
Discussion points
Beta Was this translation helpful? Give feedback.
All reactions