You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that in cases (example: #27904) where custom amp-script code from publishers causes errors, those errors bubble up into an unhandled promise rejection, and are reported to AMP Error Reporting. This adds noise to error reporting, as the underlying issue is one with publisher code, not with AMP code. These errors should be caught and reported as user errors.
It seems that in cases (example: #27904) where custom amp-script code from publishers causes errors, those errors bubble up into an unhandled promise rejection, and are reported to AMP Error Reporting. This adds noise to error reporting, as the underlying issue is one with publisher code, not with AMP code. These errors should be caught and reported as user errors.
/cc @jridgewell
The text was updated successfully, but these errors were encountered: