#CB-active-session
1 messages · Page 1 of 1 (latest)
Hi there, hmmm I haven't seen this before. Do you have any more details? Is there a specific PaymentIntent or session I could look at?
I'll see if I can log that out when it fails. At the moment I'm collecting this in Sentry:
/v3/ at line 1:143405
{snip} Session=e,n._setupSession(e,n._usesButtonElement()),e.begin(),n._isShowing=!0},this.abort=function(){n._privateSession&&n._privateSession.ab {snip}
[native code] in forEach
/v3/ at line 1:131209
{snip} -1]=arguments[a];var o=t._callbacks[e]||[];return o.forEach((function(e){var t=e.fn;if(t._isUserCallback)try{t.apply(void 0,r)}catch(e){thro {snip}
./node_modules/@sentry/browser/esm/helpers.js in i at line 73:23
Although I'm not sure that's particularly helpful....
Yeah that doesn't really mean anything to me
What's the most useful information to log here?
I'm 99% sure it's only for Apple Pay users. As we've collected 3.8K events all on iPhone safari
Hmm checking with a colleague on what would be most useful to log here
Thanks!
Okay actually we located the error message and looks like you are right that this is Apple Pay specific and is just triggered from someone spamming the button. We make a note internally that this noise can be ignored — I'm a bit surprised we don't suppress it for you.
Ah okay, that's great to know. Appreciate you looking into it!