[Snyk] Security upgrade react-native from 0.48.4 to 0.69.12

[MHxGH-ServiceAccount]

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

Snyk changed the following file(s):

• examples/SafariViewExample/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	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 in the example app.

• Bumps react-native in examples/SafariViewExample/package.json from 0.48.4 to 0.69.12

^{Written by Cursor Bugbot for commit f0cc424. This will update automatically on new commits. Configure here.}

[MHxGH-ServiceAccount]

✅ 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]

This is a massive upgrade across more than 20 major versions, representing a fundamental migration rather than a simple update. The most significant breaking changes were introduced in version 0.60.

Key Breaking Changes:

• Build System Overhaul: Version 0.60 introduced mandatory support for AndroidX and a new "autolinking" mechanism for native modules, deprecating react-native link. iOS projects are now managed by default with CocoaPods.
• Core Component Extraction: Many modules were removed from the core library and must be added as separate dependencies. This includes WebView, NetInfo, Geolocation, and Slider.
• React 18 Support: The target version 0.69 adds support for React 18, which removes deprecated APIs like ViewPropTypes and may require updates to dependencies.

Source: React Native Blog: Announcing Version 0.60
Recommendation: This upgrade cannot be performed automatically. It requires a dedicated migration effort. Use the official React Native Upgrade Helper to apply changes incrementally between versions.

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

[cursor]

Incompatible React version for React Native 0.69

The react-native upgrade from 0.48.4 to 0.69.12 creates a peer dependency conflict. React Native 0.69 requires React 18.x, but the react dependency remains at 16.0.0-alpha.12. This version mismatch will cause installation failures due to unmet peer dependencies and runtime errors if installation proceeds. The react version needs to be upgraded to 18.0.0 or later to be compatible with react-native 0.69.12.

 

[cursor]

Start script uses outdated CLI path

The start script references node_modules/react-native/local-cli/cli.js, but this path no longer exists in react-native 0.69.12. The CLI was extracted to @react-native-community/cli as part of the "Lean Core" initiative, and the 0.69.12 package exposes the CLI at ./cli.js in the package root, not in local-cli/. Running npm start or yarn start will fail with a "module not found" error after this upgrade.