fix(perf): add null check in case trace, screenTraces & httpMetric SparseArrays are cleared during module teardown

[russellwheatley]

Description

• Possible that SparseArrays are cleared during module teardown. See here: https://github.com/invertase/react-native-firebase/blob/main/packages/perf/android/src/main/java/io/invertase/firebase/perf/UniversalFirebasePerfModule.java#L45-L50

fixes #8938

Related issues

Release Summary

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

---

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 GitHub.

Project	Deployment	Actions	Updated (UTC)
react-native-firebase	Error		Mar 30, 2026 10:27am

[gemini-code-assist]

Code Review

This pull request introduces null checks in the stopTrace, stopScreenTrace, and stopHttpMetric methods within UniversalFirebasePerfModule.java. These additions prevent potential NullPointerExceptions that might occur if traces or metrics are cleared during module teardown before the JavaScript layer stops them. I have no feedback to provide.

[mikehardy]

seems like a reasonable approach
confirmed that at the JS layer the pathway is always:

1- verify arguments and such before calling down to native
2- return the result of a call to native

And in native all pathways were

1- do things
2- always return null

So adding null safety here then returning null is a graceful way to handle it

[mikehardy]

macOS CI failure unrelated, see:

• ci(macos): fix macos test runner #8947

Non-blocking