docs: warning about expo-dev-client preventing native crash reporting to Firebase #8562
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request updates the documentation to add a warning in the Expo installation section, clarifying that when
expo-dev-clientis installed, native crashes (such as those triggered bycrashlytics().crash()) will not be reported to Firebase Crashlytics during development. This is becauseexpo-dev-clientprovides 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-clientand Firebase Crashlytics, to clarify that native crash reporting is suppressed in development builds using the custom error overlay.Checklist
AndroidiOSOther(macOS, web)e2etests added or updated inpackages/\*\*/e2ejesttests added or updated inpackages/\*\*/__tests__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-clientand native crash reporting is present and clear.Think
react-native-firebaseis great? Please consider supporting the project with any of the below:React Native FirebaseandInvertaseon Twitter