Skip to content

Commit 9179820

Browse files
Add troubleshooting section to React Native Annotate Components page
Based on message from customer on Discord adding the troubleshooting steps to the docs as well. https://discord.com/channels/621778831602221064/1286059289252986940/1290353709678858371
1 parent 7206404 commit 9179820

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/platforms/react-native/integrations/component-names.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,10 @@ Here's what the resulting node would look like if your bundler had applied the p
7171

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

74+
## Throubleshooting
75+
76+
- Use `export SENTRY_LOG_LEVEL=debug` to enable debug logs. When generating the JS Bundle, you should see logs about the Sentry Metro Plugin saving and loading the default Babel transformer.
77+
7478
## Next Steps:
7579

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

0 commit comments

Comments
 (0)