Set anonymous Sentry user so alerts report users affected

[piyalbasu]

TL;DR

Sentry alerts for the Freighter extension all showed "Users: 0", so we couldn't tell how many people a given error actually affected. The cause: error events were never tagged with a user, so Sentry had no one to count. This attaches a stable, anonymous per-install identifier to Sentry events (only when error reporting is already enabled), so alerts now show real "users affected" counts. No personal data or wallet addresses are involved — it's the same opaque ID analytics already uses, so the two stay in agreement. This matches how the mobile app already works.

Implementation details (for agents)

Root cause: @sentry/browser is on v9, where sendDefaultPii defaults to false (no IP capture), and Sentry.init was never followed by a Sentry.setUser call. Every event therefore arrived with an empty user, and Sentry's "users affected" counts distinct user identifiers → 0.

What changed:

• Attach an anonymous user id during Sentry init, inside the existing SENTRY_KEY && isDataSharingAllowed consent gate, reusing the persisted analytics id (same one Amplitude uses, so counts stay aligned):
  

  freighter/extension/src/popup/components/ErrorTracking/index.tsx

  Lines 48 to 55 in 459c3af

  	});
  	// Attach a stable anonymous user ID so Sentry can report "users
  	// affected" counts. Reuses the same persisted random ID as Amplitude
  	// (helpers/metrics getUserId) so user counts stay aligned across the two.
  	// No PII / wallet address — just an opaque per-install identifier.
  	// Mirrors freighter-mobile's Sentry.setUser in src/components/App.tsx.
  	Sentry.setUser({ id: getUserId() });

• Export the existing getUserId helper so the Sentry init can reuse it rather than minting a separate id:
  

  freighter/extension/src/helpers/metrics.ts

  Line 128 in 459c3af

  export const getUserId = (): string => {

• Harden the id generator: Math.random() can yield values < 1e-6 (rendered in exponential notation, e.g. "4e-7") or exactly 0 ("0"), where split(".")[1] is undefined. That undefined would flow into Sentry.setUser({ id: undefined }) and amplitude.setUserId(undefined), reproducing "Users: 0" for that install. Fall back to "0":
  

  freighter/extension/src/helpers/metrics.ts

  Lines 113 to 117 in 459c3af

  	const generateRandomUserId = (): string =>
  	// Math.random() can yield values < 1e-6 (exponential notation, e.g. "4e-7")
  	// or exactly 0 ("0"), where `split(".")[1]` is undefined. Fall back to "0"
  	// so we never persist or hand Sentry/Amplitude an undefined user id.
  	Math.random().toString().split(".")[1] ?? "0";

Design notes:

• Gated on consent — only set inside the existing data-sharing check, and cleared by the existing Sentry.close() on opt-out.
• No PII — opaque random id, never the public key / wallet address. Same metrics_user_id localStorage key as Amplitude, so Sentry and Amplitude user counts agree.
• Mirrors freighter-mobile, which already does Sentry.setUser({ id: await getUserId() }) in src/components/App.tsx off the same shared getUserId.

Verification:

• tsc --noEmit -p extension/tsconfig.json → exit 0, 0 errors.
• Pre-commit hooks (lint + i18next-scanner) passed.
• Behavior is forward-only: existing open issues stay at 0 affected users; counts populate as new events arrive from updated installs.

Follow-up / out of scope:

• The same generateRandomUserId undefined edge case exists in freighter-mobile's generator; worth the same one-line ?? "0" hardening in that repo as a separate PR.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 459c3afc47

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[github-actions]

PR Preview build is ready: https://github.com/stellar/freighter/releases/tag/untagged-2ff63a035bea038feea7 (SDF collaborators only — install instructions in the release description)

[Copilot]

Pull request overview

This PR updates the extension’s Sentry initialization to attach a stable, anonymous per-install user identifier to error events (only when data sharing is enabled), allowing Sentry alerts to correctly show “users affected” counts.

Changes:

• Set a Sentry user { id } during Sentry initialization using the existing persisted analytics user ID.
• Export getUserId from helpers/metrics so it can be reused by error tracking.
• Harden the random ID generator to avoid producing undefined in edge cases (Math.random() exponential/zero formatting).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
extension/src/popup/components/ErrorTracking/index.tsx	Sets an anonymous Sentry user ID during init so Sentry can compute “users affected”.
extension/src/helpers/metrics.ts	Exports getUserId and hardens ID generation to avoid undefined IDs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.