Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AMP authorization delay

See original GitHub issue

Description

I’m experiencing a slowness in AMP when requesting the authorizarionUrl endpoint. The AMP HTML version of the content is taking about 20 seconds to request.

The effect of this for users is that they see all the barriers available, and after 20 seconds or so they see the correct barrier.

However, when the correct barrier is mounted, the AMP READER_ID and CLIENT_ID variables are not replaced with their actual values that AMP Engine assembles.

Example of what it looks like in markup: Markup AMP

Has anyone seen or is also seeing this problem currently?

Reproduction Steps

1 - Request the URL: https://www.google.com/amp/s/blogs.oglobo.globo.com/malu-gaspar/post/amp/bolsonaro-provoca-desconforto-no-pl-ao-defender-auditoria-nas-urnas.html

2 - Open the network view and filter by executeAmp

3 - Wait for 20 seconds until the request appears.

Relevant Logs

v0.mjs:2 Uncaught Error: No messaging channel: initMessagingChannel timeout
    at o (v0.mjs:2:982)
    at Et.createError (v0.mjs:2:202768)
    at v0.mjs:2:108592
    at v0.mjs:2:108281

error-reporting.js:205 Request channelOpen failed: invalid response from handler
bn @ error-reporting.js:205
(anonymous) @ error-reporting.js:293
messaging.js:452 Uncaught (in promise) Error: Request channelOpen failed: invalid response from handler
    at wt.v (messaging.js:452:11)
    at wt.R (messaging.js:305:12)
    at messaging.js:67:9
v @ messaging.js:452
R @ messaging.js:305
(anonymous) @ messaging.js:67
log.js:232 [AmpAnalytics <unknown id>] Inline or remote config should not overwrite vendor transport settings