#ek1338_code

1 messages Β· Page 1 of 1 (latest)

frank slateBOT
#

πŸ‘‹ 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/1296034983915294773

πŸ“ 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.

jovial talon
#

πŸ‘‹ happy to help

void basalt
#

Some more additional detail (screenshot is the response of my Java server endpoint) .
The full error (text field from discord was too short) is:

Uncaught (in promise) IntegrationError: fetchClientSecret failed with error "The fetchClientSecret function should always resolve with a client secret as a string. The function that was provided resolved with a value type of undefined."
    at embedded-checkout-outer-8413047acd0aee5f4e385f2e208bd260.js:4:14077
jovial talon
#

πŸ‘‹ happy to help

#

would you mind sharing a link to your test site?

void basalt
#

It is all local, so I can not share, sorry

jovial talon
#

can't you use something like ngrok to tunnel?

void basalt
#

And on the Dashboard, all requests for creating this session come back green, so from server side checkout-session wise it should be fine

#

I am not familiar with that ngrok tooling sorry

jovial talon
jovial talon
#

I think you're just returning the string

#

instead of a json { client_secret: "cs_test_xxxx" }

void basalt
#

Great observation! Argh, and I even tried it yesterday with client_secret. But, it is actually clientSecret. Tried it with that json key and now it renders. Always those little things, ha. Thx for gr8 support!

jovial talon
#

let me know if you need any more help

void basalt
#

Thanks! Maybe a short follow-up. I try to shortcut the implementation of /create-shipping-options by just returning {type:'object', value: {succeeded: true}} on my server (as in tutorial).
But the stripe form somehow seems to know that no actual update was done. I will implement that later, but interesting how it knows that i did not actually update my session

#

(I've also entered sth. in Address line 2 - same result)

jovial talon
#

I'm not sure I fully follow

#

would you mind elaborating a bit more?

void basalt
#

I am not sure why the Stripe widget gives me the error Shipping details missing. Please update the Checkout Session with a complete shipping address and try again. even though I filled out every detail in the Shipping address form

#

my assumption is that stripe somehow sees, that my server is actually not really updating the stripe-session on the server-side (but only returning the simple json). And therefor the error

jovial talon
#

I think you just need to add Address Line 2

void basalt
#

No, I tried that, same error

jovial talon
#

let me check

void basalt
jovial talon
void basalt
#

Yeah, exactly πŸ‘ Okay, that was also my assumption. Probably stripe will somehow see, that I just was doing the shortcut (returning plain json) without actually updating the session. Alright, will implment that later, thanks!

jovial talon
#

sure