#chris-valentine_error

1 messages ยท Page 1 of 1 (latest)

indigo haloBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1339030884699078739

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

frank knot
#

Hello! Can you link me to the page where you're seeing this error?

fiery ridge
#

yes will need to give you log in info and such

frank knot
#

Oh, in that case can you give me the Checkout Session ID?

fiery ridge
#

let me see

#

its the live site that has the issue, i'd have to deploy something with the a console.log to get it unles syou know a way to do that without. i can see if i get teh same error locally with a live key

frank knot
#

You can look in your request logs in the Stripe Dashboard to see the API requests being made.

fiery ridge
#

oh ok let me do that

frank knot
#

Or you can use the web dev tools to inspect the network requests to get the Checkout Session ID coming from your server.

fiery ridge
#

req_E8K1HNcRaNfAWL

#

is it that

#

cs_live_a17dbVlQrqlMLsDG5ngsup6Ul0CFiJ4xBDGwuRYMTmfchraY7xqpDMSOND

#

or maybe that

frank knot
#

Yep, that's it.

#

And what publishable key are you using on the frontend?

fiery ridge
#

pk_live_51OhXYKLlO1pQlrfoIfvtQN0FYv3j3hMmoOpfgFceMnEVvWlSrffiHUv133io3nwDcREozOjQuUQAwfTLCfoQhc0M00IRFkIGce

frank knot
#

Those match up and should work together just fine. You're 100% certain that's the actual key being used on the page? You've confirmed by searching for and vetting all instances of pk_ using the web dev tool's search function?

fiery ridge
#

i searched my code base. i dont know "web dev tool" is probably something i shoudl be using that i'm not

frank knot
#

When you load the page in your browser, the dev tools in the browser are what I'm referring to.

fiery ridge
#

ah i'll check it, my code though shows a single place. the other three have spaces in the name and are actually remarked comments

frank knot
#

Yeah, but the code on the actual site could be different somehow, like due to a silent build or deploy failure or who knows what. ๐Ÿ™‚

fiery ridge
#

so this is in chrome web dev?

frank knot
#

Yeah, up in the top right of the dev tools there's a โ€ขโ€ขโ€ข button. Press that and there should be a search option in the menu.

fiery ridge
#

ok one moment

#

definitely see a mix

#

probably this i'd guess , eh

#

perhaps vercel's redeploy is not actually clearing env variables

frank knot
#

Yep, that seems like the culprit.

fiery ridge
#

I'll do a full new deploy and stop using redeploy

#

but i think i'm good here, i should be able to figure this out now that I know how i can see that ๐Ÿ™‚

frank knot
#

Cool, happy to help!

fiery ridge
#

thanks tremendously, especially for the search feature ๐Ÿ™‚

#

full new deploy did fix this fyi ๐Ÿ™‚

frank knot
#

Nice!