Skip to content
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/platforms/react-native/integrations/component-names.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,13 @@ Here's what the resulting node would look like if your bundler had applied the p

The Sentry browser SDK will pick off the value from these `data` attributes and collect them when your components are interacted with.

## Troubleshooting

- If component names are missing in the reported events, check if the annotations are present in the JS bundle generated by Metro. You can text search in the bundle for the `data-sentry-component` key.
- To add the annotations `config.transformer.babelTransformerPath` is required to be set in the Metro config before calling `withSentryConfig`.
- Function `getSentryExpoConfig` returns the configuration with the Sentry Babel Transformer set, do not overwrite `config.transformer.babelTransformerPath`.
- Use `export SENTRY_LOG_LEVEL=debug` to enable debug logs and observe if Sentry detected the default transformer and if Sentry Babel Transformer was executed.

## Next Steps:

- Lear more about Sentry's React Native [Metro bundler plugin](/platforms/react-native/manual-setup/metro/).
Loading