Skip to content

Isolate NativeDevSettings load #52821

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

Closed
wants to merge 1 commit into from
Closed

Conversation

sbuggay
Copy link
Contributor

@sbuggay sbuggay commented Jul 25, 2025

Summary:
While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moved the NativeDevSettings load into the one function that needs it, probably not the best solution because if this function gets called in this mode we will crash still, but it works for now.

Changelog: [Internal]

Differential Revision: D78952284

Summary:
While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moved the NativeDevSettings load into the one function that needs it, probably not the best solution because if this function gets called in this mode we will crash still, but it works for now.

Changelog: [Internal]

Differential Revision: D78952284
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 25, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D78952284

sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 25, 2025
Summary:

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moved the NativeDevSettings load into the one function that needs it, probably not the best solution because if this function gets called in this mode we will crash still, but it works for now.

Changelog: [Internal]

Differential Revision: D78952284
sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 25, 2025
Summary:

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moved the NativeDevSettings load into the one function that needs it, probably not the best solution because if this function gets called in this mode we will crash still, but it works for now.

Changelog: [Internal]

Differential Revision: D78952284
sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 28, 2025
Summary:

Hardens RN to running in mismatched opt/dev modes.

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moves the NativeDevSettings load into the one function that needs it.

Changelog: [Internal]

Differential Revision: D78952284
sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 29, 2025
Summary:

Hardens RN to running in mismatched opt/dev modes.

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moves the NativeDevSettings load into the one function that needs it.

Changelog: [Internal]

Reviewed By: rubennorte

Differential Revision: D78952284
sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 30, 2025
Summary:

Hardens RN to running in mismatched opt/dev modes.

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moves the NativeDevSettings load into the one function that needs it.

Changelog: [Internal]

Reviewed By: rubennorte

Differential Revision: D78952284
sbuggay added a commit to sbuggay/react-native that referenced this pull request Jul 30, 2025
Summary:

Hardens RN to running in mismatched opt/dev modes.

While adding an opt native/dev js mode to fantom, LogBox was trying to load NativeDevSettings when it didn't exist because of mode mismatch.

This is the only location it's happening, so this just moves the NativeDevSettings load into the one function that needs it.

Changelog: [Internal]

Reviewed By: rubennorte

Differential Revision: D78952284
@react-native-bot
Copy link
Collaborator

This pull request was successfully merged by @sbuggay in 807f0b6

When will my fix make it into a release? | How to file a pick request?

@react-native-bot react-native-bot added the Merged This PR has been merged. label Jul 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported Merged This PR has been merged. p: Facebook Partner: Facebook Partner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants