TerminalConnectTypes.Internet doesn't work for browser app

[kyleabens]

Platform

• Web
• iOS
• Android

Describe the bug
Using TerminalConnectTypes.Internet does not work for ionic apps in the browser. Seems to only work for iOS or Android apps.

Expected behavior
This should be possible on the browser

await StripeTerminal.discoverReaders({
    type: TerminalConnectTypes.Internet,
    locationId: ***********
 });

Using Function:

• Payment Sheet / Payment Flow
• Apple Pay
• Google Pay
• Identity (@capacitor-community/stripe-identity)
• Terminal（@capacitor-community/stripe-terminal）

[rdlabo]

Please check out our demo.It has been available on the Web since v6.2.0.
https://github.com/capacitor-community/stripe/releases/tag/v6.2.0

[kyleabens]

@rdlabo I'm having a hard time seeing if I need to add something else for it work on web. I'm on v6.2.1 and I can confirm the below promise never resolves or throws an error.

await StripeTerminal.discoverReaders({
    type: TerminalConnectTypes.Internet,
    locationId: ***********
 });

[kyleabens]

Could it be because TerminalEventsEnum.RequestedConnectionToken listener never fires after await StripeTerminal.initialize({ isTest: false }) ?

[rdlabo]

First, this “Expect Happy Path - Internet” can discover the device (it's my device at hand, so it's offline).

https://capacitor-community-stripe.netlify.app/tabs/terminal

I can guess that the locationId is wrong, the token is wrong, etc., but I confirm that the plugin itself works.

[kyleabens]

Where can I see the code for that specific "Expect Happy Path - Internet" demo ? I can never get it to fire on the browser but I can on the app.

[rdlabo]

Sorry for late. Demo code is be at this repository:
https://github.com/capacitor-community/stripe/tree/main/demo/angular

[shiv19]

@kyleabens It might be that issue #407 happens on web too where Stripe SDK might actually call onFetchConnectionToken twice after initialize and this plugin currently can only handle 1 call to RequestedConnectionToken when tokenProviderEndpoint has not been specified.

Do you still need help with this?

[rdlabo]

@kyleabens The latest version of #407 solves this problem, so this problem may be solved. Please try the latest version once.