🐛 fix unexpected exception when no entry type is supported in PerformanceObserver

[BenoitZugmeyer]

Motivation

Following #2855 and #2818, we are using more granular PerformanceObserver. We observe less entry types in the PerformanceObserver from performanceCollection, and in the new performanceObservable, we observe a single type at once.

We observed that in old versions of Safari, if all entry types supplied to .observe(..) are unsupported, an exception is thrown: entryTypes contained only unsupported types. Illustration:

// assuming 'resource' is supported but not 'longtask'
new PerformanceObserver().observe({ entryTypes: ['resource', 'longtask'] }) // succeeds
new PerformanceObserver().observe({ entryTypes: ['longtask'] }) // throws

Changes

To work around this issue, this PR wraps .observe(..) calls in try/catch blocks to prevent the SDK from crashing.

Testing

• Local: even on BrowserStack we don't have the exact Safari version that triggers this issue (it should be Safari 11 with OSX 10.11 or below, see notes here). But I tested that we still collect performance resource entries in the Safari 11 version provided by BrowserStack.
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[BenoitZugmeyer]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, median merge time is 11m

Commit 51567db0e6 will soon be integrated into staging-30.

Use /to-staging -c to cancel this operation!

[dd-devflow]

🚂 Branch Integration: This commit was successfully integrated

Commit 51567db0e6 has been merged into staging-30 in merge commit 059bf94ebd.

Check out the triggered pipeline on Gitlab 🦊