#peter-belbin_unexpected

1 messages ¡ Page 1 of 1 (latest)

terse crestBOT
solid owlBOT
#

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.

terse crestBOT
#

👋 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/1270439754156085339

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

kind ferry
#

However, now I have established that the card element is being populated with a publishable (test) key, and yet, the problem is still randomly happening.

This is a problem on two fronts. One is our customer experience. The other is our testing automation that's failing on a reasonably consistent basis.

Note: this issue has only become noticeable in the last 2 weeks or so. It seems that something on the Stripe end is failing to respond randomly.

zealous bear
#

Hi, I highly recommend that you migrate away from our CardElements, legavy product and use PaymentElement. This is a more modern integration and can handle much more for your automatically. You can learn more about it here: https://docs.stripe.com/payments/payment-card-element-comparison

As far as the issue at hand, what do you mean by 'failing'? Are you seeing an error? What is exactly happening? How can I reproduce this issue?

kind ferry
#

I suppose you could recreate the error. What we have is storybook that's got a bunch of web app UI 'stories' that it serves up, and some of those have an <iframe> element containing the card element, which, until recently, has rendered nicely, and allowed a screen capture to be taken for detection of unintended changes to the UI. So, what we've been seeing is that sometimes, requests that the card element is making are not being responded to, and this pretty much gums up the works, preventing a screen capture from being able to be taken successfully. We have some debugging added/enabled, to highlight when this failure to get a response is happening, and that's what it's showing - ie: that a request is sometimes being made to Stripe's systems, but, it's not always getting a response.

#

The stack of software involved in this is: storybook (which serves up the test pages), then you have, as client to that, a thing called storycap, which leverages puppeteer to remote-control an instance of the Chromium browser (headless).

#

Now, what I have done is run the storybook server locally, and then, take a scenario's URL and plug that into a normal Chrome browser. With the dev-tools open, looking at the 'networking' tab, sometimes, I see that a request receives no response from Stripe's servers.

#

I have verified that the publishable key is being used, which was the question at the end of the thread of discussion that was had yesterday.

#

The error is observable happening in both the continuous integration build environment as well as engineer's individual systems, both in the office and remotely. Again, this issue has only become noticeable relatively recently. Our code projects use version locks on the modules that we're using, so it's not a matter of some code having changed on our side that's causing this issue.

zealous bear
#

Can you share a testable URL for me so I can reproduce this issue on my end?

#

I have not heard this report so I need to be able to repoduce to further debug this

kind ferry
#

Sorry, say that last sentence again?

zealous bear
#

I have not seen this reported so I would need to be able to repdouce this to further debug the issue. Sorry for the confusion

kind ferry
#

Let me inquire as to how that might be done, if at all.

terse crestBOT
kind ferry
#

still asking about how to expose it, if possible....

shadow shore
#

Hello
Can you elaborate what you mean by "how to expose it"?

kind ferry
#

ie: how to make what I'm using to see the issue able to be used by yourselves, to see it happening yourself.

shadow shore
#

You'd need to find the pattern that triggers this behavior. You can add more logging in your code and see if that exposes anything.

kind ferry
#

Well, what I have currently is evidence via logging output that sometimes, a resource is not resolved. It happens seemingly on a random basis, however. And, of course, the chromium browser is actually managing the requesting of the resources.

shadow shore
#

When you say it is not resolved, any specific errors you're seeing?

kind ferry
#

The API that I'm using to show the list of URLs that the browser needs to resolve does not provide me with how it fails. But, interactively, using dev tools, I have been able to see that sometimes, the request simply does not get any response.

#

when I say 'not resolved' it means: the response has not been received.

shadow shore
#

I see. Unfortunately as this is sporadic and not reproducible, I don't think we'll be able to help much on discord.

I'd recommend opening a support ticket via https://support.stripe.com/?contact=true and providing as much details as you can including the your stripe code, all logs you've collected and example time windows where you've seen these failures..

Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

kind ferry
#

I have spoken with the person I report to, and they've approved a) looking into using the PaymentElement instead of the CardElement, and b) putting some effort into seeing whether something that's shareable can be created to demonstrate the issue, if it's found to still be an issue after item a) is looked at.

#

So, I guess I have some work to do, either way, before I contact you folks again, on this topic.

shadow shore
#

Gotcha. Yeah sorry we couldn't help much with this