This is my function: export async function getServerSideProps(contexto) {
const { id } = contexto.params;
const movies = await getMovie(id);
const cardMovies = await getMovies();

return {
props: {
movies,
cardMovies,
},
};
}

If I was you, I would try to explain the issue in english, that would probably greatly increase your chances of getting an answer.

jajaajja sorry

can you make a minimal reproduction repository?

Of course

i dont think this is minimal reproduction

what do they mean then?

vercel?

he meant create a new repository where the bug persists

throwing away irrelevant code making it "minimal" and only focuses on the bug

Ah vale

with a correct id passed to /movies/[id] i got this error

which is due to you using fallback inside gssp which is not allowed

removing the fallback prop gives me this

which i think is working well

an invalid id will give this page in development and likely a 500 page on deployment

which you can fix by updating movie.service.js so it can handle invalid id as well

Sorry, I was testing. but without the fallback it doesn't work either

or this

export async function getServerSideProps(contexto) {
    try {
        const { id } = contexto.params;
        const movies = await getMovie(id);
        const cardMovies = await getMovies();

        return {
            props: {
                movies,
                cardMovies,
            },
        };
    } catch {
        return { notFound: true }
    }
}

are you on localhost?

yes

On localhost it works fine, but try this link: https://ssr-six-beta.vercel.app/

404

interesting, i can reproduce the bug too and dunno what's wrong

it should work

maybe you should try to contact [vercel help](https://vercel.com/help), this is probably a bug in vercel or nextjs

Okay, thanks for your time. I'm going to contact them