Known Issue: ‘script amp-onerror’

Isn’t it the second time in a few months that changes by the AMP team or the AMP validator team broke stories?
There were a bunch of issues recently with amphtml-version being incorrect due to a change on the AMP side.

I wanted to thank you guys for putting out a patch so quickly, but you must be seriously annoyed that you have to work overtime to “fix” something broken by another team ??.

Don’t they test on Web Stories when they put out a new version of the validator?
Seems like a pretty basic test they should run…

Thank you a lot for sorting the issues so promptly…You guys are awesome!!

This interim solution helped to see the errors valid in the tool but every time when google hits the page from the webmaster the page is first considered as “invalid” web story and we have to fetch manually and test live its a valid page.

– Google first attempt is crawl the page is invalid so the pages don’t consider as valid amp or amp story-
– if we fetch manually then it comes a valid but how many we fetch every day and we cant control what pages google is considering them as valid.

check the screenshots here.

Google first time hit – https://jmp.sh/U8ucb4t invalid webstory
Manually testing the page – https://jmp.sh/LwUrrlh

the work around is for plugin but not for google bot to index the pages.

All the stories that we are publishing are considered as invalid and going waste.

– Joanna

Google first time hit – https://jmp.sh/U8ucb4t invalid webstory
Manually testing the page – https://jmp.sh/LwUrrlh

@thenewsvoice Hmm, in the first screenshot, the Google search console validator defines the entry as a web story. Although invalid.
In the second case, a valid page, but as a simple amp page.

AMP Page is always the case if we render the page using test live. It wont show as amp valid story if we test that but not amp story.

The main concern is, the first visit to the page is invalid so google dont pick it up.

Hi Luckyna and co,

I get the exact same error (story isn’t validated by Google). Know you are working hard on this, I appreciate any news!

Cheers,
Nico

@nicolapallotta after install mini-plugin too?

@luckynasan Why can’t roll back the version of the Search Console validator to a working version? And install the new version after fixing the errors.

The plugin is developed

By Google

• This reply was modified 3 years, 5 months ago by eddie.
• This reply was modified 3 years, 5 months ago by eddie.

…

• This reply was modified 3 years, 5 months ago by eddie.

Its sad that web stories used to bring thousands of clicks per day.Now this error happens and not even a single click per day on even view.

Thanks everyone chiming so far, really appreciate the feedback!

Unfortunately this specific issue wasn’t caught in any testing due to a combination of various factors.

Glad to hear the mini-plugin is working for you all so far. If you haven’t installed it yet, make sure you do so to ensure stories being valid AMP. Please note that there might be some caching involved in Search Console reports and similar tools.

While most of our team is currently out due to a US holiday, we should be able to provide an update regarding this bug in the coming days.

Hi everyone, quick update!

The issue has been resolved on the validator side, but it will take some time to fully take effect.

If you check your stories using the AMP validator chrome extension or through validator.amp.dev, you should no longer see these errors starting today, whereas Search Console will have it by the end of the week.

In other words, keep the mini-plugin activated until the end of the week. Afterwards you can safely remove it.

Tnx!

Hello Everyone, this issue has been resolved in Search Console as well. The mini-plugin can now be safely removed accordingly on your site.

I will close out this thread, so if you continue to experience issues, please submit a new topic to the Web Stories forum.

Thank you for your patience while we investigated and fixed this issue, and thank you for using Web Stories!