Hybrid Index Amp pages always shows the amp version in production.

[yassinebridi]

Bug report

Describe the bug

When creating a hybrid Index Page, with a getStaticProps function, the index page in production will always show the amp page in domain.com and not in domain.com/index.amp

This works as expected in dev mode, where the non amp page will show in localhost and amp page in localhost?amp=1

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to https://github.com/yassinebridi/amp-prod, the master branch where the problem exist.
2. deploy

Expected behavior

For the index page to show the non amp page first, and show the amp page, when going to domain.com/index.amp

Links

• This is the repo and the production url for the problem

  • https://github.com/yassinebridi/amp-prod
  • https://amp-prod-gp02joast.now.sh/

• This is the commit without the getStaticProps(where it works as expected):

  • https://github.com/yassinebridi/amp-prod/tree/c023a071aa94101844783640539102abab8cdc5a
  • https://amp-prod-qq7ksp86z.now.sh/

System information

• Version of Node.js: v14.2.0

Additional context

This behavior doesn't occur in dynamic pages, where i would have getStaticPaths too, i didn't test it though.

[tomaszrondio]

is there any solution? I have similar problem but with dynamic pages generated on build. On runtime it works fine.

[yassinebridi]

@tomaszrondio i'm not sure if this PR #17461 fixes the problem or not, try it out.

[tomaszrondio]

@tomaszrondio i'm not sure if this PR #17461 fixes the problem or not, try it out.

if I did it correctly it does not. I added changes directly to node_modules/next/dist/export/worker.js

[yassinebridi]

if I did it correctly it does not. I added changes directly to node_modules/next/dist/export/worker.js

No just upgrade Next to this release:

https://github.com/vercel/next.js/releases/tag/v9.5.6-canary.1

[tomaszrondio]

nope. I does not help. I opened new issue yesterday about it. #18128

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.