#bartosz-connectjs-iframe
1 messages ยท Page 1 of 1 (latest)
What's the exact error you're seeing?
if it's not in the iframe it's working fine:
bad one seems to be served via varnish while good request response is from cloudfront
bartosz-connectjs-iframe
๐ You're my first developer ever asking about this brand new library/tool so I need to spend time debugging this first which will take a while.
I'm assuming we might not support iframes yet but looking
looks like the cookie is different while using an iframe
csrf part of it
working:
stripe.csrf=_Vl5RgSe4y33RleHLsYcPeWfm14nvz0zhmJCbqznqccA47IvXJfxhulKw2yEFOOwo46nKgAvtSPT1f6NQ3Kruzw-AYTZVJw-gchmK88niEohxzlypVklbBb0FGNQa3zcYtVQfdnc8g%3D%3D
not working:
stripe.csrf=3XJoxB5WQ92S6bpFGmEnBigm5o5wwnOwKMynKL_4zZkgyKOtRl9RdozlLq6ws9iLbjfa-ldS-6B9exvLUG3P5Tw-AYTZVJx4jdJdV53zz2XAEQ15gxmi9xoT_EdHMzeDhiRrp5DMbQ%3D%3D
sorry still digging into this
I've confirmed we don't intend to support iframes today at least
@hexed summit can you share an account id that you're testing this on?
it's live and test mode for this one:
acct_1Nwst8L68qPlt7ST
do you need any pk keys?
nah that's enough
That account id doesn't make sense, it's not connected to any platform and it's not a Connect platform
pk_live_51Nwst8L68qPlt7STtXYUDsqP2TFkkcPIYjGAnxAOrDP5IvJDAqnYD1VxJgVeQLWyT0AQ7sUxTxHnNWDaJHFBid0r00Ylqv09q5
that's the pk key we use from that account
it's not a connected account, but the account of the platform itself
hum
the errors we see is when our platform account tries to create an element for the payouts
That's not the key from a platform
You're either mixing up your integration/accounts or sharing the wrong information
yeah, I might mix the terms... please tell me precisely what you need so I can give it to you ๐
Right now you shared an account id acct_1Nwst8L68qPlt7ST and the API key from that account. This account is not a Connect platform. It's also not an account connected to a platform.
So to me this is just an unrelated account that has nothing to do with your real integration/debugging right now.
If it's really the key you're using, there has to be something wrong with your integration because you use the keys from an account that doesn't have access to the Connect product
I get that, but that's not the account that you're using Connect.js on
it's not a Connect platform. It doesn't have any connected accounts. It can't use Connect.js
ok, my bad...
acct_1K8oRRDConGnCqgo
pk_live_51K8oRRDConGnCqgoWH6IYu5bCibsr234VLC9YJ7df6XHVYlB7vp7U1S9lzhSfe4cCblXcwZcGBuflA0jbvGYeZF600rbQaUfAK
got two similar accounts and it's late
no worries and thanks we're still looking
Just to confirm: you have this in production in an iframe?
yeah
currently using test mode, but it's also happening in live
<?xml
version="1.0" encoding="UTF-8"?>
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>MRXCKCWPJHCK84FG</RequestId>
<HostId>iHYezeCQbK/QkTZFHThOKmqTGYzjzCQtekt6qyR+lU5nsZ/d8FDHx65KMF+PQOUZOtPcnfn4QqY=</HostId>
</Error>
this is from test mode... what exactly returns that error?
cloudfront?
yeah we think we're calculating something wrong with the internal scripts in an iframe
technically we never planned to support iframes but looks like it worked before
until today I guess...
yeah but that's a bug since we weren't taking iframes into account
we're looking into a potential fix now and then we'll figure out usage and likely ask all users to move off of iframes
and what about payment element? it still works in the iframe:
PaymentElement is a completely different product in a completely different JS library
ok, makes sense
is this something relatively quick to fix now?
It will take a while to fix, but we're working on it right now. It's not a bug in our backlog since we clearly caused production issues for you
in the long term we can go away from iframes, but not something we can do in near future
is it possible to receive updates about it via email?
or some official channel?
Best approach is to talk to support: https://support.stripe.com/contact. Mention this problem and the thread and that there's an ongoing investigation and they will keep you updated!
ok, thanks!
sure thing and sorry for the trouble, definitely not something we're happy causing ๐ฆ