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
This error first surfaced last summer, and has reached the first page of errors in AMP Error Reporting
Error: null is not an object (evaluating 'a.split')
at split (https://raw.githubusercontent.com/ampproject/amphtml/2004030010070/src/url.js:198)
at url (https://raw.githubusercontent.com/ampproject/amphtml/2004030010070/src/url.js:222)
at (https://raw.githubusercontent.com/ampproject/amphtml/2004030010070/extensions/amp-ad-custom/0.1/amp-ad-custom.js:73)
at (https://raw.githubusercontent.com/ampproject/amphtml/2004030010070/extensions/amp-a4a/0.1/amp-ad-network-base.js:155)
The error occurs when trying to .split a URL string. The source of the URL is a call to AmpAdNetworkBase#getRequestUrl, which gets the URL from its element's src attribute. Below this access, there is a devAssert with the message Invalid network configuration: no request URL specified. When that happens in production, however, there is no handling of a missing request URL.
I suspect the component fails to display anything in this failure case. If I understand correctly and this is a misconfiguration on the part of the publisher, maybe this should be caught and logged as a user error?
/cc @ampproject/wg-ads
The text was updated successfully, but these errors were encountered:
This error first surfaced last summer, and has reached the first page of errors in AMP Error Reporting
The error occurs when trying to
.split
a URL string. The source of the URL is a call toAmpAdNetworkBase#getRequestUrl
, which gets the URL from its element'ssrc
attribute. Below this access, there is adevAssert
with the messageInvalid network configuration: no request URL specified
. When that happens in production, however, there is no handling of a missing request URL.I suspect the component fails to display anything in this failure case. If I understand correctly and this is a misconfiguration on the part of the publisher, maybe this should be caught and logged as a user error?
/cc @ampproject/wg-ads
The text was updated successfully, but these errors were encountered: