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

[expo-dev-menu] Make internal runtime undebuggable #19269

Merged

Conversation

lukmccall
Copy link
Contributor

Why

Takes advantage of facebook/react-native#34489.
It'll improve our integration with Hermes inspector - users don't have to reload their app anymore to see correct sources.

How

Set enable debugger on internal runtimes.

Test Plan

I couldn't test it properly because our basic template crashes with RN 0.70.

@lukmccall lukmccall requested a review from Kudo September 27, 2022 13:39
@expo-bot expo-bot added the bot: suggestions ExpoBot has some suggestions label Sep 27, 2022
@lukmccall lukmccall changed the title [menu] Make internal runtime undebuggable [expo-dev-menu] Make internal runtime undebuggable Sep 27, 2022
Copy link
Contributor

@Kudo Kudo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • ios works.
  • android crashes because react-native 0.70 introduces jsi breaking change and it is compatible with the bundled reanimated. however, the change for android looks good to me.

thanks for the fix 👏

@lukmccall lukmccall force-pushed the @lukmccall/client/make-internal-runtimes-undebuggable branch from 98b7a9c to b821b0a Compare September 28, 2022 14:29
@lukmccall lukmccall merged commit 50e5afb into main Sep 28, 2022
@lukmccall lukmccall deleted the @lukmccall/client/make-internal-runtimes-undebuggable branch September 28, 2022 14:29
@expo-bot
Copy link
Collaborator

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries


Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:


Generated by ExpoBot 🤖 against b821b0a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: suggestions ExpoBot has some suggestions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants