#sircrog_unexpected

1 messages ยท Page 1 of 1 (latest)

nimble otterBOT
#

๐Ÿ‘‹ 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/1314345854945202177

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

slow compass
nimble otterBOT
vernal harness
slow compass
#

Hi ๐Ÿ‘‹

#

I do see it as an option, yes

#

"[Violation] Permissions policy violation: payment is not allowed in this document." fair assessment, yes

vernal harness
#

Yeah, the code sandbox is using iframes, which can cause a lot of problems, and it probably also lacks a Payment Method Domain.

slow compass
#

On there I do see Google Pay

#

Which does not match the result of our demo/test application

vernal harness
#

Ah, so it was the iframe causing the problem then.

#

Can you link to your demo/test applicaiton?

slow compass
#

I'm going to make sure the instantiations match

#

I can't share it publicly, unfortunately

#

Thus the codesandbox

vernal harness
#

If I can't see the page it's going to be much harder to help, but I'm happy to answer questions for you if I can!

slow compass
#

If you're able to see the account based on the acct_ id used, th test application is one of the registered domains

#

A repeat error in console is Unable to download payment manifest "https://google.com/pay".

vernal harness
#

That usually doesn't cause a problem, but it sometimes can. Are you using any iframes on the page in question?

slow compass
#

No

vernal harness
#

Same publishable key as the code sandbox?

slow compass
#

yep

#

publishable key + acct_ id match

vernal harness
#

I think I found your demo page. Mostly gray? Lots of options that can be changed? If so, there's an uncaught exception in the console that might be an issue. I'm not seeing the payment manifest errors you mentioned, though, so I might be in the wrong place.

slow compass
#

That's the one

#

Set field mode: Stripe Payment Elements

#

Stripe Auth: acct_1QNKNoGGzvyaknof

vernal harness
#

Do I need to also put the publishable key in or no?

slow compass
#

No it's hardcoded to our platform publishable key

#

Does stripe.js have a debug output mode of any kind?

vernal harness
#

No.

#

I'm seeing a config-missing-public-key error in the console.

slow compass
#

That's unrelated, but if you'd like to quiet it you can use public key ewr1-9hRP3YPyMsbYJCPNt9amDy

vernal harness
#

So it's really strange, because I'm seeing Apple Pay show up even though I'm in Chrome, and I'm still not seeing the payment manifest errors.

slow compass
#

Are you seeing apple pay in a Payment Element or in an Express Checkout Element?

vernal harness
#

Payment Element.

slow compass
#

That's expected

#

I believe that should work in newer Chrome

vernal harness
#

I should be seeing Google Pay, not Apple Pay. And attempting to use Apple Pay throws an error.

#

I'm at a loss, honestly. I'm not sure why this is behaving this way, or why I'm not seeing the same behavior you are.

#

To clarify, are you seeing Apple Pay on your end in Chrome?

slow compass
#

I am, yeah

vernal harness
#

What happens when you try to use Apple Pay?

slow compass
#

I'm currently waiting for edge cache invalidation so am on an older version of this application using an express checkout element

#

express checkout is trying to show the apple pay button but it's just appearing as a blank space

#

There are other Apple Pay implementations further down the page that won't work of the public key I gave you .. but for one which does work, Apple Pay works as expected on Chrome

vernal harness
#

Yeah, to be clear, while Apple supports Apple Pay in other browsers now, Stripe doesn't. Apple Pay should not show up in Express Checkout Element or Payment Element in Chrome. I have never seen this happen before, and it's very, very strange.

slow compass
#

Same with Google Pay

#

Okay yep, Interesting

vernal harness
#

I wonder if it's because you're loading Apple's Apple Pay JS library on this page, maybe?

#

Perhaps that's loading something that makes Stripe.js think it's in a browser that supports native Apple Pay?

slow compass
#

Hard for me to say of course, but seems plausible

vernal harness
#

Let me test something...

#

Ah, yep, that's it:

#

I blocked the Apple Pay SDK URL with dev tools and reloaded, now it works as expected.

#

That's wild. ๐Ÿ˜…

slow compass
#

Fascinating!

#

Second stripe.js bug in two days ๐Ÿ˜‰

vernal harness
#

I will flag that internally, but in the meantime I recommend you only load the Apple Pay SDK or Stripe's Apple Pay-related stuff, not both at the same time.

slow compass
#

Good to have a resolution here. Great find!

vernal harness
#

Happy to help! Glad I found that, because it was really bothering me!

slow compass
#

Same here. Big relief.

#

Thanks for your help and have a great day

vernal harness
#

You too!

#

Oh, I forgot to mention that I smiled when I noticed your test page's favicon. ๐Ÿ™‚

slow compass
#

You should click the [DOS MODE] button