Feat: Fallback to stacktrace parsing

[lucas-zimerman]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Use Sentry React Native stack trace parser when ReactNativeLibraries.Devtools?.parseErrorStack is not available.

The change did no impact on stack trace grouping. Still, I opted to always prefer ReactNativeLibraries.Devtools?.parseErrorStack to avoid any kind of break change.

💡 Motivation and Context

In the near future, ReactNativeLibraries.Devtools?.parseErrorStack will no longer exist.

💚 How did you test it?

Error with RN Parser https://sentry-sdks.sentry.io/issues/5005282269/events/a7874a2c8efb405caa1a81d0c0f3caab/?project=5428561
Error with Sentry Parser https://sentry-sdks.sentry.io/issues/5005282269/events/45fee3cad3cc43d3821a4121fa4ed80d/?project=5428561

📝 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

Close #5943

I don't think this PR needs any changelog, since it gives no value to end users at the moment since they are not impacted by it.

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• Feat: Fallback to stacktrace parsing by lucas-zimerman in #5946

• fix(ci): Bump Node to 22 in size-analysis and testflight workflows by antonis in #5954
• feat(playground): Open Sentry in desktop browser from Expo apps by antonis in #5947
• chore(core): Bump sample app to React Native 0.84.1 by antonis in #5941
• Size analysis for React Native SDK by alwx in #5949
• chore(deps): bump lodash from 4.17.23 to 4.18.1 by dependabot in #5953
• chore(deps): bump yauzl to ^3.2.1 by antonis in #5950
• chore(deps): bump brace-expansion to ^2.0.3 by antonis in #5951
• chore(deps): bump @xmldom/xmldom to fix XML injection by antonis in #5952

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

	Fails
🚫	Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 7935207

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Fallback returning empty array can wipe exception frames
  • Added a check in symbolicate() to return null when sentryFrames.length === 0, preventing the truthy empty array from triggering replaceExceptionFramesInException and wiping original stack traces.

Or push these changes by commenting:

@cursor push 052a53a070

Preview (052a53a070)

diff --git a/packages/core/src/js/integrations/debugsymbolicator.ts b/packages/core/src/js/integrations/debugsymbolicator.ts
--- a/packages/core/src/js/integrations/debugsymbolicator.ts
+++ b/packages/core/src/js/integrations/debugsymbolicator.ts
@@ -92,6 +92,9 @@
     );
 
     const sentryFrames = await convertReactNativeFramesToSentryFrames(stackWithoutInternalCallsites);
+    if (sentryFrames.length === 0) {
+      return null;
+    }
     return await fetchSourceContext(sentryFrames);
   } catch (error) {
     if (error instanceof Error) {

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[antonis]

Other than the bot feedback LGTM

[antonis]

LGTM

[sentry]

Sentry Build Distribution

App Name	App ID	Version	Configuration	Install Page
Sentry RN	io.sentry.reactnative.sample	8.7.0 (82)	Release	Install Build

[sentry]

Bug: The fallback stack parser from @sentry/react may not support Hermes bytecode-offset stack traces from production React Native builds, causing symbolication to fail silently.
_{Severity: MEDIUM}

Suggested Fix

Ensure the fallback parser can handle all common React Native stack trace formats, including Hermes bytecode offsets. This could involve using a more appropriate RN-specific parser or extending the existing defaultStackParser and adding test cases that explicitly cover production Hermes stack formats (e.g., p@1:132161).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/core/src/js/integrations/debugsymbolicatorutils.ts#L4

Potential issue: The new fallback logic uses `defaultStackParser` from `@sentry/react`,
a browser-oriented parser. This parser is not guaranteed to handle all React Native
stack trace formats, particularly the Hermes bytecode-offset format (e.g., `p@1:132161`)
common in production builds. While tests confirm it handles V8-style Hermes traces,
there is no coverage for the bytecode format. When the primary
`ReactNative.Devtools.parseErrorStack` is unavailable and an error with a bytecode stack
occurs, the fallback will likely fail to parse the frames. The current implementation
handles this by returning an empty array, which causes symbolication to be silently
skipped, leading to unsymbolicated stack traces in Sentry reports for production errors.

_{Did we get this right? 👍 / 👎 to inform future reviews.}