Skip to content

Conversation

@elliette
Copy link
Member

@elliette elliette commented Jan 20, 2026

Fixes #9622

Fixes a potential race condition in setupDimensions where, if it was called twice in a row the first call would set _computingDimensions = true and the second call would immediately return, regardless of whether the first call had completed leading to missing data in our analytics.

Also fixes #9623:

Removes guards to setupUserApplicationDimensions (and _computeUserApplicationCustomGTagData, which it calls). This function is called every time the VM service connection changes, therefore we were not re-computing the dimensions for a newly connected app leading to incorrect data in our analytics.

Note: catches errors in both methods so that if setting up our analytics fails in any way we won't crash the app.

@elliette elliette requested a review from a team as a code owner January 20, 2026 22:53
@elliette elliette requested review from bkonyi and srawlins and removed request for a team January 20, 2026 22:53
Copy link
Contributor

@srawlins srawlins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stale user app data in analytics when the VM service connection changes Missing analytic dimensions on app startup

2 participants