What is this about?

Our diagnostic state snapshots that we attach to Sentry events do not include the extension ID. We should update them to include it. This would help us differentiate between errors from our published extension, and errors from side-loaded extensions or forks that we don't support.

Scenario

No response

Design

No response

Technical Details

Add the extension ID to the Sentry state.

We can get the id from browser.runtime.id. We can't rely upon the origin for the ID; the origin should include the ID on Chrome, but on Firefox the origin is a random UUID. browser.runtime.id should get us the correct ID on all browsers.

Threat Modeling Framework

No response

Acceptance Criteria

• The extension ID is included in Sentry state snapshots, and visible in error reports.

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response