fix(performance)!: inconsistent handling when trace does not exist on the web compared to native platforms #773
Labels
breaking change
Breaking change
package: performance
platform: android
Android platform
platform: ios
iOS platform
platform: web
Web platform
Milestone
Comments
ebarooni
added
platform: android
robingenz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The behavior of the methods such as
stopTrace(...)andincrementMetric(...)is different on Android and iOS compared to web when a trace is not found. On the native platforms the methods throw an error when a trace for the given traceName does not exist. On the web however, the methods return void.The text was updated successfully, but these errors were encountered: