Amp is not working in homepage

I think I face same issue with yours.

Is the error is something like this?

https://ibb.co/T4vfy7N

Can anyone please help us?
for this: https://healtholine.com/amp/

We already create a ticket for this fatal error. Our development team is working on it. It will be fixing in our next update.

Reference: : https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/4412

• This reply was modified 4 years, 7 months ago by Ahmed Kaludi.

@ahmedkaludi Dear, Can i know when the issue will be fixed? And when is your next update?Do we need to remove the amp for homepage? Please suggest

in few minutes

I have the same problem.

@ahmedkaludi Dear its not fixed yet, the same problem persists. kindly fix it asap

The same here! And the canonical tag are duplicated!

@ahmedkaludi dear, is there any update on this?

@ahmedkaludi I tried the below change as per your git hub and the site started working.
https://github.com/ahmedkaludi/accelerated-mobile-pages/commit/4c504100e5bc133312620082e8701919f1186d06

Now I am getting an amp validation error: The tag ‘link rel=canonical’ appears more than once in the document.

This appears on all pages except the homepage

The tag ‘link rel=canonical’ appears more than once in the document I’m getting this problem too. When will the update come?
@ahmedkaludi

• This reply was modified 4 years, 7 months ago by O?uzhan.

This was caused by a recent update from Yoast. We have just pushed an update that has solved this issue.

Here are the two important things you need to do:
1. Make sure the AMPforWP is updated to 1.0.43
2. Make sure “Yoast” is selected in the SEO section for proper compatibility, see: https://take.ms/r8a4L

Let me know if that fixes the issue?

Same error after updating Yoast. Waiting for bug fix plz

No, The tag ‘link rel=canonical’ appears more than once in the document The error persists. Please offer a solution.
Screenshot : https://prnt.sc/s7nfdo

Try this:
1. Resave AMP options panel
2. Clear Cache from any cache plugins or any server cache
3. check again.