Verify Firebase Performance Monitoring integration and data collection

[jamespepper81]

Summary
We need to verify that Firebase Performance Monitoring (FPM) is correctly integrated across the Analyzer app, that traces and network requests are being captured, and that metrics appear in the Firebase console for both development and production builds.

Background
FPM helps us monitor app performance in real-world use. There are past reports of missing traces or incomplete network instrumentation; this issue ensures FPM is installed, configured, and actively reporting.

Goals

• Confirm FPM SDK is initialized correctly in the app lifecycle.
• Verify custom traces and automatic network requests are recorded.
• Ensure metrics and traces appear in the Firebase console for dev and prod builds.
• Add acceptance criteria and clear test steps so QA can validate.

Acceptance Criteria

• Firebase SDK initialization code exists and runs on app start.
• At least one custom trace is visible in the Firebase Performance console after following the test steps.
• Network requests (HTTP/HTTPS) generated by the app appear as HTTP metrics in the console.
• Release and debug/dev builds both produce reports (with appropriate sampling) visible in Firebase.
• Any missing instrumentation is documented with suggested code changes.

Environment

• Repo: BitSleuthAI/Analyzer
• Platforms to test: web (if applicable) and any mobile targets (specify Android/iOS if included)
• Branch: indicate which branch to test (e.g., main / release)

Test Steps

1. Build and run a development/debug build of the app (describe commands or dev server if needed).
2. Trigger app flows that:
   • Launch the app (app start trace).
   • Perform a sample API call (e.g., request wallet/tx data) to generate network traces.
   • Execute a heavy computation or long-running operation to trigger custom traces (if available).
3. Wait 10–15 minutes for Firebase to process perf data, then check the Firebase Performance console for:
   • New traces (custom and app-start).
   • HTTP / network request metrics associated with the app.
4. Repeat with a production/release build (or deployed environment) and confirm similar traces are captured.
5. If traces do not appear, capture SDK logs from the app and any console errors and attach to the issue.

Suggested tests/data

• Sample wallet address or test API endpoints to exercise network calls
• Timestamps and user IDs (if needed) to filter console data

Logging & troubleshooting

• Where to find client logs (browser console, mobile logcat / Xcode logs).
• Example of how to enable verbose Firebase logging (if applicable).
• Suggested checks for initialization (e.g., confirm firebase.initializeApp(...) called, confirm Performance monitoring enabled via getPerformance()).

Checklist

• Confirm Firebase initialization on app start
• Verify at least one custom trace is visible
• Verify network requests appear in Performance console
• Confirm both dev and prod builds send data
• Attach logs/screenshots if issues are found
• Recommend code changes or documentation updates if instrumentation is incomplete

---

• Labels: bug
• Assignees: jamespepper81
• Projects: Analyzer
• Type: Bug