e.userData is undefined

Unanswered

Northeast Congo Lion posted this in #help-forum

Northeast Congo LionOP

2023-09-18T03:47:40.000Z

Weird error occurs when I click a Next.Link element. It says "e.userData not found". userData is a variable used in my middleware and another similar layer that is used elsewhere. It's also used as a prop in a page that shouldn't be relevant as the link leads neither to nor from it.

This error doesn't occur on my local machine, only with the built version when it's deployed. (of course, this is a problem plaguing my Production server). Any idea what might be going on here?

https://i.gyazo.com/1ac10357736e02f1194911da30492bdc.png

https://i.gyazo.com/b295a11a64e5abc99e7d2f6b70860ec1.png

it also goes away when I refresh. So click link -> error-> refresh -> all good

52 Replies

Spectacled bear

2023-09-18T03:54:19.000Z

userdata property of an object, but the property does not exist

Northeast Congo LionOP

2023-09-18T03:55:46.000Z

Well, why is it being created in my local version and not in the built version?

And why is it fine when I refresh

Spectacled bear

2023-09-18T03:58:31.000Z

Different server configurations or version?

Barbary Lion

2023-09-18T03:59:04.000Z

cna yuo give all details as to where and how you are deploying

Northeast Congo LionOP

2023-09-18T03:59:11.000Z

Sure

Again, not 100% sure what code is causing this problem

so I'll show what I can as far as code

I'm deploying using SST to AWS

Barbary Lion

2023-09-18T03:59:47.000Z

also you should share all relevant code around userData

Northeast Congo LionOP

2023-09-18T03:59:57.000Z

Yup hang on am doing so

Spectacled bear

2023-09-18T04:01:18.000Z

The e.userData not found error is occurring because of a difference in the way that serverless applications are handled by AWS compared to traditional web applications

Northeast Congo LionOP

2023-09-18T04:02:07.000Z

thanks, chatgpt

    if (props.userData.tier != "free" && linksList.length > 4){
        linksList = [<Link href="/links" className={styles.primaryButton} key="0">Manage Links</Link>]
        newLinkButton = <></>
    }

@Barbary Lion this is the most "Suspect code" here

Spectacled bear

2023-09-18T04:02:25.000Z

What

Northeast Congo LionOP

2023-09-18T04:02:44.000Z

I say that because this is the only time there's an ".userData" anywhere

Spectacled bear

2023-09-18T04:03:03.000Z

uhm

Northeast Congo LionOP

2023-09-18T04:04:34.000Z

But what's weird is that it's erroring every time a Link is clicked, not just the code that's running this page

in a diff part of the code we have this:

let userData = resultVal.split("#")
    if (userData.length === 3){
        emailVerified = userData[2] === "true"
    }

    let resultVal:string = ""
    if (result.val){
        //validate the cookie
        validCookie = true
        resultVal = result.val as string
    }

also have this code

export async function userFromCookies(req:any):Promise<User|null>{
    const userData = await verifyAuth(req);
    if (!userData) {
        console.log("No user data, request: ", req)
        return null
    }
    let userString = userData.val as string;
    let userID:number = parseInt(userString.split("#")[1])
    let userName = parseInt(userString.split("#")[0])

    let prisma = new PrismaClient()
    //get user data from the database
    let foundUser = await prisma.user.findUnique({
        where: {
            id: userID
        }
    })
    await prisma.$disconnect()
    return foundUser
}

Barbary Lion

2023-09-18T04:14:39.000Z

in the if statement add to the beginning "props.userData &&", same with teh second block of code below

also check out phind.com it is the best programming chatbot I've used, better than gpt4.

Northeast Congo LionOP

2023-09-18T04:14:57.000Z

Is it possible to have code from one part/page of your application erroring on a diff page

is SpeedyFriend67 phind.com?

Barbary Lion

2023-09-18T04:18:02.000Z

nope probably chatgpt 3.5 which sucks

Northeast Congo LionOP

2023-09-18T04:18:08.000Z

Fair nuff

So I modified some code

the error message changed after a deploy

so now I can narrow it down a little, I think, though there's still another error

it's using "o" now, but similar error

so yeah. Now having 2 issues. Problem 1:
e.userSerialized is undefined (I think this is happening in a react.useState thing)

Problem 2: Totally unknown location saying "o" is undefined

Barbary Lion

2023-09-18T04:23:28.000Z

u should disable bundling and minification for production build so u can set breakpoints and read the code in production

Northeast Congo LionOP

2023-09-18T04:24:12.000Z

That's probably a good idea. Any idea how to do that in SST?

Let me ask in SST

seems to be coming from any case where a props object is used in a react.useState

Northeast Congo LionOP

2023-09-18T04:33:31.000Z

Yeah this is very weird... props aren't being received at all when navigating with Link

Barbary Lion

2023-09-18T04:37:16.000Z

you mean a state variable is passed in as a prop?

Northeast Congo LionOP

2023-09-18T04:37:31.000Z

Hang on, let me give an example

userDataSerialized is passed in via props in this example

    let imgWidth = 200
    if (props.userDataSerialized){
        imgWidth = props.userDataSerialized.imageWidth
    }
let [imageWidth, setImageWidth] = React.useState(imgWidth)

this will behave as if imgWidth is 200

there's a property called "authorized" that's handled a similar way

    if (!authorized){
        return (<>
            {genHead("Unauthorized", "You are not authorized to access the controls page.")}
            <main className={`${styles.main} ${inter.className}`}>
                    <h1>You are not authorized to access the controls page.</h1>
            </main>
        </>)
    }

This causes the page to show this message every time unless refresh is used.

Barbary Lion

2023-09-18T04:41:18.000Z

how is authorized handle in a similar way

Northeast Congo LionOP

2023-09-18T04:41:30.000Z

 const {authorized, id, controllers} = props

basically something about the props is what's going on.

if I were to suspect, it's that getServerSideProps is not being called when you click a Link

but only on built versions for some reason

Northeast Congo LionOP

2023-09-18T06:03:49.000Z

Fixed.

It's a problem with 13.4 it seems