You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation uses GoogleWalletClient.savePass. It is therefore only possible to use this plugin with Google Wallet. If users chose to use another wallet application or even run on an Android Device without the Google Service Framework available, this plugin obviously won't work at all.
I would hence propose to additionally add the option to use the "traditional" Android way and share the pass (either as transit JSON or as PkPass) as an INTENT a compatible application can receive. For this use case, a PkPass file is likely more eligible than raw transit JSON.
Steps to reproduce :
use a device without GSF
open SNCF Connect
open a ticket details page
you won't see the Add to wallet button since the GoogleWalletClient.getPayApiAvailabilityStatus will return unavailable
be sad you can't import your TGV journey into your wallet since you don't use Google 😢
The text was updated successfully, but these errors were encountered:
Hello, have you examples of other wallets you are using ? The name of this plugin is flutter_google_wallet so indeed, this is not here about the wallet feature of sncf connect but the flutter plugin to access the google wallet
In my case I'm using fWallet, but there are other PkPass applications too : https://search.f-droid.org/?q=pkpass. Unlike a deeplink to Google's Android APIs, using PkPass (which at least SNCF connects also supports, though on Apple devices only), PkPass files enable users to use the Wallet implementation of their choice.
That's the way Google Wallet works, and that's the main audience of our app. But we could give also the pk pass, maybe with another button. Do you know if there is a simple way to detect the presence of fWallet on a device ?
The current implementation uses
GoogleWalletClient.savePass
. It is therefore only possible to use this plugin with Google Wallet. If users chose to use another wallet application or even run on an Android Device without the Google Service Framework available, this plugin obviously won't work at all.I would hence propose to additionally add the option to use the "traditional" Android way and share the pass (either as transit JSON or as PkPass) as an INTENT a compatible application can receive. For this use case, a PkPass file is likely more eligible than raw transit JSON.
Steps to reproduce :
Add to wallet
button since theGoogleWalletClient.getPayApiAvailabilityStatus
will return unavailableThe text was updated successfully, but these errors were encountered: