Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no duplicate meta tag but receive: conflicting amp tag "meta" with conflicting prop name="viewport" #7284

Closed
oahehc opened this issue May 8, 2019 · 2 comments
Closed

no duplicate meta tag but receive: conflicting amp tag "meta" with conflicting prop name="viewport" #7284

oahehc opened this issue May 8, 2019 · 2 comments

Comments

@oahehc
Copy link

oahehc commented May 8, 2019

Bug report

Describe the bug

Received this error without creating any viewport meta tag.
And also no duplicate meta tag at client side.
Found conflicting amp tag "meta" with conflicting prop name="viewport". https://err.sh/next.js/conflicting-amp-tag

To Reproduce

  1. start a new Next.js project
  2. create ./pages/index.js as below 
    import { withAmp } from 'next/amp';

export default withAmp(() => {
  return <div>withAmp test</div>
});
  3. create ./pages/_document.js as below 
    import React from 'react';
import Document, { Html, Head, Main, NextScript } from 'next/document';

export default class MyDocument extends Document {
  render() {
    return (
      <Html>
        <Head />
        <body>
          <Main />
          <NextScript />
        </body>
      </Html>
    );
  }
}
  4. yarn dev
  5. received this error in the terminal
    Found conflicting amp tag "meta" with conflicting prop name="viewport". https://err.sh/next.js/conflicting-amp-tag

Expected behavior

no error in the terminal

System information

  • OS: macOS
  • Browser: chrome
  • Version of Next.js: 8.1.0
@timneutkens
Copy link
Member

I believe this was fixed already on next@canary. cc @ijjk

@ijjk
Copy link
Member

ijjk commented May 8, 2019

Yup, this has been fixed in the latest next@canary closing this. Feel free to reply if you're still seeing this after trying next >= v8.1.1-canary.25

@ijjk ijjk closed this as completed May 8, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@timneutkens @oahehc @ijjk