-
-
Notifications
You must be signed in to change notification settings - Fork 344
Expo Router performance auto instrumentation #2754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Maybe it works OOTB because its based on one of our integrations that we already support, likely has to be tested but in the case, offering 1st class support. |
Let's start by testing if it works OOTB and later prioritize again in case it does not work. |
Hi @krystofwoldrich do you have any update on this item? |
Hey @k1n8t1c thanks for flagging this - we're already in the holiday slowdown, but expect updates after the holidays! |
Hey @krystofwoldrich please do update us on this issue. I'm working on an Expo project and would definitely appreciate an update on this. |
My team is also implementing sentry for Expo and we hit the same roadblock. |
Hey everyone, not sure if this is the preferred route, but in case it helps someone. Working with expo router, I tried a couple of "hacks",
|
Thank you, everyone, for the messages and for letting us know about your interest, we are currently finalizing the deprecation of the And following that, we will work on new features like Expo Router Automatic Instrumentation. |
Todos:
|
Docs are at https://docs.sentry.io/platforms/react-native/performance/instrumentation/expo-router/ sentry-react-native/samples/expo/app/_layout.tsx Lines 21 to 23 in df6100a
|
Description
There is a new router for RN apps Expo Router, currently in RC.
It's built on top of react-navigation so maybe auto instrumentation will work out of the box, but we need to check that.
The text was updated successfully, but these errors were encountered: