-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
React Native Debugger
is now useless with Expo SDK 49+, since remote debugging is disabled.
#11065
Comments
Following since this is a definite pain point on React Native. We have a bare RN app (not using expo) but I've had relative success installing this (very simple) package to continue to use Apollo Client DevTool in The package: https://github.com/gusgard/react-native-devsettings |
@jasongaare thanks for that library. I'm attempting to get it working, but I don't think it works with Expo in managed workflow with the expo go app. It may work with dev builds. I imagine that would be basically the same as a bare RN app at that point. Here is my post in RND: jhen0409/react-native-debugger#765 All that being said, it would be nice to see some input from the apollo community, as their official docs lean very heavily on RND. |
I've just merged #11364 which shows a way of inspecting the Apollo Client cache that at least worked for me when testing. I can also connect the chrome debugger to the app (I updated to Expo 49 and it's using Hermes) without problems, so this might have been fixed upstream by now? |
How Did you make it work for Chrome Debugger? |
@AugustoAleGon no, but with Flipper. |
any news about this problem? :( |
@6ase yes, you can use the flipper debugger with the Apollo Client plugin like described above. |
Issue Description
Afaik, apollo client users were predominantly depending on
React Native Debugger
to use Expo.Now that Expo SDK 49 has disabled remote debugging, that no longer seems to be an option, and I haven't found any immediate options for integrating the apolo dev tools to the hermes engine.
Not having access to the apollo dev tools is a huge hinderance.
@phryneas tagging you, as per your request.
Link to Reproduction
https://blog.expo.dev/expo-sdk-49-c6d398cdf740
Reproduction Steps
No response
The text was updated successfully, but these errors were encountered: