docs: warning about expo-dev-client preventing native crash reporting to Firebase

[algoORgoal]

Description

This pull request updates the documentation to add a warning in the Expo installation section, clarifying that when expo-dev-client is installed, native crashes (such as those triggered by crashlytics().crash()) will not be reported to Firebase Crashlytics during development. This is because expo-dev-client provides a custom error overlay that catches and displays errors before they are sent to Firebase. The warning helps developers avoid confusion when testing crash reporting in development builds.

Related issues

Fixes #8561

Release Summary

Added a documentation warning about the interaction between expo-dev-client and Firebase Crashlytics, to clarify that native crash reporting is suppressed in development builds using the custom error overlay.

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

This change is documentation-only. To verify, review the updated Expo installation section in the documentation and confirm the warning about expo-dev-client and native crash reporting is present and clear.

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 9, 2025 2:28pm

[CLAassistant]

All committers have signed the CLA.