🚨 Error: Cannot read property '__AMP_TOP' of null

[ampprojectbot]

Details

Error report: link
First seen: Oct 15, 2020
Frequency: ~ 1,031/day

Stacktrace

Error: Cannot read property '__AMP_TOP' of null
    at win (src/service.js:285:9)
    at getTopWindow (src/service.js:159:8)
    at getService (src/service.js:338:62)
    at getAmpdoc (src/service.js:224:17)
    at getServiceForDocOrNull (src/service.js:70:9)
    at Services (extensions/amp-analytics/0.1/cookie-writer.js:54:34)
    at extensions/amp-analytics/0.1/amp-analytics.js:244:15

Notes

@cramforce modified src/service.js:285-285 in #23767 (Aug 7, 2019)
@choumx modified src/service.js:153-162 in #10131 (Jun 28, 2017)
@rsimha modified src/service.js:338-341 in #21212 (May 16, 2019)
@dvoytenko modified src/service.js:223-224 in #30634 (Oct 15, 2020)
@dvoytenko modified src/service.js:70-70 in #30634 (Oct 15, 2020)
@zhouyx modified extensions/amp-analytics/0.1/cookie-writer.js:40-55 in #18406 (Sep 28, 2018)
@rsimha modified extensions/amp-analytics/0.1/amp-analytics.js:244-253 in #21212 (May 16, 2019)

Seen in:

• 10-16 Beta (2313+2)
• 10-16 Experiment-A (2313+2)
• 10-16 Experimental (2313+2)
• 10-22 Nightly (2244)
• +2 more

Possible assignees: @dvoytenko, @cramforce

/cc @ampproject/release-on-duty

[samouri]

@rcebulko: is it ok to close bugs like this in which the link no longer points to a valid error?
Same with #30855

[rcebulko]

See #30945 (comment) for general guidance.

In this case, there are numerous variants of this error message (incl. #28264 and ampproject/error-reporting#50) so it's being tracked elsewhere. Should be safe to close.