#ash_ece-not-rendering
fiery roseBOT
👋 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/1291066541680492685
📝 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.
- ash_api, 2 days ago, 26 messages
- ash_wallet-element, 4 days ago, 5 messages
- ash_code, 5 days ago, 9 messages
royal dagger
Hi 👋
Can you share a front-end where I can view the Express Checkout Element?
sleek axle
It's running in a dev environment, I can send screenshots ?
let me know if you need something more specific
sorry I left out the file extensions but they're .png images
royal dagger
Wait a sec...you are already showing Apple & Google Pay, what is it you are doing?
sleek axle
no sorry
those elements are not from Stripe
I was implementing a custom UI
but we are choosing to use the Express Checkout Elements from stripe instead
royal dagger
Okay so the first step would be, in your dev environment, create a clean basic page and only render the Express Checkout Element following the exact code we have in this guide:
https://docs.stripe.com/elements/express-checkout-element
sleek axle
Another possibility is that we are also rendering a Card Element from stripe,
However, I have contacted support recently and they informed me that I could render both the Card Element and the Express Checkout Element in the same page
royal dagger
Yeah there's nothing wrong specifically with rendering both. But can you try starting from a blank page?
sleek axle
okay can I will try
can we leave this open ?
it will only take 5 mins for me to test
royal dagger
We close threads due to inactivity but we usually wait longer than 5 minutes so you should be fine
royal dagger
Oh wait, are you using an HTTPS URL scheme?
royal dagger
But, as you can see, those errors are being thrown when your client makes requests to play.google.com
Something is blocking those requests
sleek axle
Yep
royal dagger
Unfortunately this isn't a Stripe code issue, as far as I can tell
sleek axle
yeah okay thank you
Still, do you have a list of most common issues blocking express checkout element rendering ?
so I can at least cross them out
royal dagger
Unfortunately no. One thing you can try is to quickly spin up a version running locally on your computer. Then use a tunnelling service like ngrok to quickly create an HTTPS public URL route and see if you get similar errors