Skip to content

Conversation

@sharifhh
Copy link
Contributor

@sharifhh sharifhh commented Aug 6, 2025

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

In React Native 81 Hermes changes their runtime access pattern.

💡 Motivation and Context

In React Native 81 Hermes changes their runtime access pattern.
so this checks if new hermes runtime is available it uses it, otherwise it uses old code.

💚 How did you test it?

I installed Sentry on React Native 81 project and did a build, it didn't work.
I applied this patch then it worked.

I also tried the patch with react native 80 and 79, and all went well.

📝 Checklist

  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing
  • No breaking changes

🔮 Next steps

@sharifhh sharifhh changed the title Fix React Native 81 Hermes Runtime Access Pattern Support React Native 81 Aug 6, 2025
@sharifhh sharifhh changed the title Support React Native 81 Support New Hermes Runtime Access Pattern Aug 6, 2025
@lucas-zimerman
Copy link
Collaborator

Thank you for your contribution!

The CI errors are likely related to you using the branch main as the main source of the PR.

Would you be able to use another branch name for the PR and keep the main branch from your fork without the changes for this PR?

@sharifhh
Copy link
Contributor Author

sharifhh commented Aug 7, 2025

hyg #5051

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