FirebaseError: Performance (performance/invalid attribute value)

[LanderBeeuwsaert]

Operating System

Any user OS (me on Windows 11)

Environment (if applicable)

any environment (me on Chrome)

Firebase SDK Version

11.9.1

Firebase SDK Product(s)

Performance

Project Tooling

Angular + AngularFire + Firebase application

Detailed Problem Description

We have consistently these errors:

FirebaseError: Performance: Attribute value mat-cell.mat-mdc-cell.mdc-data-table__cell.cdk-cell.cdk-column-message.mat-column-message.ng-star-inserted is invalid. (performance/invalid attribute value). at t.putAttribute (https://www.acro-companion.com/chunk-3YNIXL5M.js:15:57905) at t.addWebVitalMetric (https://www.acro-companion.com/chunk-3YNIXL5M.js:15:59358) at t.createOobTrace (https://www.acro-companion.com/chunk-3YNIXL5M.js:15:59137) at https://www.acro-companion.com/chunk-3YNIXL5M.js:15:60739

this is not a performance trace that we created ourselves. I suppose this is one of the default (out-of-the-box) created traces for webVitals?

Steps and code to reproduce issue

This is probably happening all over. Maybe because the attribute value that is trying to be set is too long?

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[k-thornton]

I get this kind of error in my console constantly, ever since dropping in Firebase Performance Monitoring into my Nextjs-based website (using TailwindCSS for styling)

FirebaseError: Performance: Attribute value span.font-display.mt-6.block.max-w-5xl.text-5xl.font-medium.dark:text-neutral-dark-950.tracking-tight.text-neutral-950.text-balance.sm:text-6xl is invalid. (performance/invalid attribute value).

These attributes are all valid on an individual basis. I have no idea why it's concatenating all of my variables together with periods, and then saying that that giant string is invalid.

[dlarocque]

Hey @k-thornton @LanderBeeuwsaert Could you please share concrete steps that can be followed to reproduce this issue? We'll follow those steps and confirm whether it's a bug. You mentioned this is probably happening all over. Does this mean that anyone following the documented set up (Get started with Performance Monitoring for web) for any app will see these errors?