Benji Soar

hi @sshropshire ... it's definitely 100% reproducible, first thing I'll do tomorrow is recreate it whilst checking the HTTP responses and get back to you :)

Hi @sshropshire. At the point I attempt to add the duplicate (test) payment method, I can see a GraphQL network request go out to https://payments.sandbox.braintree-api.com/graphql with the following payload:- ```...

@sshropshire further to this, and just an observation (not strictly a bug), but when managing multiple payment methods via the drop-in and deleting all of them, returning to the main...

@sshropshire great stuff! really appreciate all the hard work you and the team are putting into this, especially removing the DropInRequest from the DropInClient constructor :)

@sarahkoop @danielebart I can confirm that this still appears to be in issue with drop-in:6.2.0. This is in our Sandbox environment with test cards: 4000000000001091 and 4000000000001109. Seemingly anything that...

Also the same occurs when choosing Google Pay as the payment method (for a non network tokenized card). Again, I only take the first response as all associated Activities (should!)...

Further to this and referring back to my closed [issue](https://github.com/firebase/extensions/issues/621) I raised in May last year I can also confirm that the creation of a partitioned table still doesn't appear...

Brilliant, thanks @dackers86 :) ... I'll create a new issue ... should arrive within the next hour or so, although it will be quite similar to issue [621](https://github.com/firebase/extensions/issues/621) I suspect...

New issue created #1059 - please let me know if I can provide any further information.

@sshropshire, @scannillo I'm at my wits end with this one, but I appear to be having the same issue. This happens for me 100% of the time at the same...