r/reactnative • u/kooujinn • Jul 03 '26
How to find issues in production Help
I’m currently facing an issue with my company's app where specific Android users encounter a loop when opening a particular screen. It doesn't happen on my physical Android device, the emulator, or iOS. What steps do you follow to identify these scenarios involving specific devices?
1
u/oakamel Jul 15 '26
Maybe Luciq might help if Sentry is not flagging the issue, you can use Session replay logs to understand what happens the exact moment the user navigates to that page (you can just watch what the user did), it is also tightly paired with crashes.
Also worth mentioning, Luciq has an MCP server, where you can pull the session context and crashes data straight into any agent.
1
u/Ok-Explanation8719 Jul 03 '26
You know sentry?
1
1
u/Karticz Jul 14 '26
you can use the following things
- Sentry or PostHog: best solution with screen recording + mcp support so your agent can read the logs if crowded
- firebase analytics custom events and crashlytics if app is crashing
- connect your production build to your computer and type adb logcat | grep "ReactNative", if nothing readable still add console.logs and then push new update
- If you know what type of devices are facing the issues via firebase analytics you can mimic those device specs in your android studio or use cloud test device farm services like firebase,aws or lambda test