it could be complaining that one if your varables that you are .maping on isn't a list and maybe undefined for its prerendering

also your suspense here is useless as it won't wait for anything as the child isn't async and doing fetching there

hello, thank you for your response.

i have narrowed down the issue to my database env not returning anything, as you have said, even though it seems ENVs are defined correctly in the repository. this would explain why it's happening on all pages where data is fetched, which is almost all of them.

cheers for noticing the redundant Suspense boundaries, i forgot to remove them.

so, i have modified my github action by hardcoding the variable into a .env file, used by the build. the full build step is now as follows:

-   name: Build Next.js app
    run: |
        touch .env
        echo POCKETBASE_URL="https://pocketbase.funkysundays.com" >> .env
        npm run build

however, even with a local .env for the runner to build from, without using github variables or secrets, it still throws the same error for each page that uses fetched data from the database. i tried again on my laptop to build locally, and it goes through with success. are there any other possibilities?

i have not included variables that are used by client interactions, assuming for a build only step that they aren't needed. could this be the issue?

EDIT:
i have tried
- node v20 lts, v21.x
- defining variables globally, in job, in step, hardcoding the values, using secrets and variables
- touching a .env file with the envs
- mirroring my build attempts locally which have all succeeded
- using github cache
- looking in nextjs repository issues
- looking in forums here
- rebuilt the entire deploy workflow using different code

i'm not sure what else i can do here

Where are you hosting your db with, and could they be somehow blocking gh actions (and what db client are you using)

i'm using a pocketbase instance hosted on an ubuntu vps, behind nginx reverse proxy

i will look to see if pocketbase blocks github actions somehow

i mean, i would hope it would error instead of return nothing 😭

indeed, it's very strange

just tried a fresh project for testing: https://github.com/sebygreen/testing-github-actions, and it builds fine...i am very confused. errors were returned correctly when there were some, database logs show correct access, and workflow goes through with success. the database URL is the same, and works this time. i think i will ask the pocketbase community as well, as i suspect it may be something to do with it's usage

ah sounds good, i am glad its all solved now!