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.

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

Next.js 13.4.13 getServerSideProps returns undefined #3800

Open
5 tasks done
ktranish opened this issue Nov 11, 2023 · 1 comment
Open
5 tasks done

Next.js 13.4.13 getServerSideProps returns undefined #3800

ktranish opened this issue Nov 11, 2023 · 1 comment

Comments

@ktranish
Copy link

Before opening, please confirm:

  • I have checked to see if my question is addressed in the FAQ.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

App Id

d3hoxczt0g35g3

AWS Region

eu-north-1

Amplify Hosting feature

SSR

Frontend framework

Next.js

Next.js version

13.4.13

Next.js router

Pages Router

Describe the bug

  • getServerSideProps returns undefined.
  • pageProps returns an empty object
  • This is happening on occasion which makes it very difficult to debug.

Expected behavior

Return data consistently from getServerSideProps

Reproduction steps

  1. Create a next.js app with getServerSideProps
  2. Upload to amplify
  3. View the page on an incognito window and refresh 1-5 times

Build Settings

No response

Log output

No response

Additional information

No response

@richie42690
Copy link

richie42690 commented Nov 20, 2023

@nytrek I'm having a similar issue that I've been debugging for two days and it only happens in production. Can't replicate in local environment. I use params and searchParams in my main page components. They only come through for dynamic routes, [dynamic]/some-page. If I have a page like this /some-page, those parameters are just null. I'm using the app folder which is probably different than what you're doing but similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants