Skip to content

[Snyk] Security upgrade react-native from 0.50.1 to 0.69.12#37

Open
MHxGH-ServiceAccount wants to merge 1 commit intomasterfrom
snyk-fix-58b2e28866cc03f835544fde6d92d98b
Open

[Snyk] Security upgrade react-native from 0.50.1 to 0.69.12#37
MHxGH-ServiceAccount wants to merge 1 commit intomasterfrom
snyk-fix-58b2e28866cc03f835544fde6d92d98b

Conversation

@MHxGH-ServiceAccount
Copy link

@MHxGH-ServiceAccount MHxGH-ServiceAccount commented Dec 30, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • examples/BiometricAuthExample/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  170  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling


Note

Updates dependency to align the example app with a newer React Native version.

  • Bumps react-native from 0.50.1 to 0.69.12 in examples/BiometricAuthExample/package.json

Written by Cursor Bugbot for commit 07c7220. This will update automatically on new commits. Configure here.

@MHxGH-ServiceAccount
Copy link
Author

MHxGH-ServiceAccount commented Dec 30, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@MHxGH-ServiceAccount
Copy link
Author

Merge Risk: High

This is a massive upgrade across 19 major versions, introducing numerous significant breaking changes. This is a major migration effort, not a simple version bump.

Key Breaking Changes:

  • AndroidX Migration: React Native v0.60 and later require Android projects to migrate to AndroidX, as the old Support Library is no longer supported. [2, 8]
  • Core Component Extraction: Many components (like AsyncStorage, WebView, NetInfo) were removed from the core package and must now be installed from community packages and imported from their new locations. [9, 15]
  • Autolinking: The react-native link command is deprecated and replaced by automatic linking for native modules, which requires changes to the project setup. [2, 6]

Recommendation: Do not attempt to upgrade by just changing the version number. Use the official React Native Upgrade Helper to see a detailed diff of all the file changes required between your current version and the target version. [1, 3, 4]

Source: React Native Upgrade Helper

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

"dependencies": {
"react": "16.0.0",
"react-native": "0.50.1",
"react-native": "0.69.12",
Copy link

Choose a reason for hiding this comment

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

React version incompatible with upgraded React Native

Upgrading react-native from 0.50.1 to 0.69.12 introduces a peer dependency incompatibility. React Native 0.69 requires React 18.x, but the react dependency remains at version 16.0.0. This will cause npm/yarn installation failures or runtime errors due to API differences between React 16 and React 18. The react-test-renderer at 16.0.0 also needs to be updated to match.

Additional Locations (1)

Fix in Cursor Fix in Web

"dependencies": {
"react": "16.0.0",
"react-native": "0.50.1",
"react-native": "0.69.12",
Copy link

Choose a reason for hiding this comment

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

Start script references nonexistent CLI path

The start script references node_modules/react-native/local-cli/cli.js, which existed in React Native 0.50.1 but was restructured in later versions. React Native 0.69.12 has the CLI entry point at ./cli.js in the package root. After this upgrade, running npm start will fail with a "module not found" error. The script needs to use npx react-native start or reference the correct CLI path.

Additional Locations (1)

Fix in Cursor Fix in Web

"dependencies": {
"react": "16.0.0",
"react-native": "0.50.1",
"react-native": "0.69.12",
Copy link

Choose a reason for hiding this comment

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

Deprecated Babel preset incompatible with React Native 0.69

The babel-preset-react-native package at version 4.0.0 was deprecated and replaced by metro-react-native-babel-preset in newer React Native versions. React Native 0.69 uses the Metro bundler with the new babel preset structure. The outdated preset will cause transpilation failures when building the app, as it doesn't support the syntax and transforms required by React Native 0.69.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants