#ben_unexpected

1 messages · Page 1 of 1 (latest)

wraith gazelleBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1443581555082657965

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

knotty basin
#

Which Element are you using? Payment Element?

devout heath
#

I believe it's the Payment Element, I might need to double check though

knotty basin
#

if it is that, then Google Pay isn't supported in webviews there

devout heath
#

Just checking, not supported by stripe?

knotty basin
#

yes, currently

devout heath
#

perfect thank you 👍

#

Ah just heard back, we are using the express element

#

Express Checkout Element

knotty basin
devout heath
#

The thing is the same app works in non-production with no issues

#

And the same google account works with our old flow in production (using barclays payment provider) so I believe we've configured the google side already

wraith gazelleBOT
knotty basin
devout heath
#

What I mean is we've already done those steps and verified they're working with our previous integration

earnest moat
#

hey there 👋 I'm taking over as my colleague needs to step away 🙂

#

just getting up to speed on this!

#

can you confirm if you're using a modern version of Android System Webview (version 137 or higher)?

devout heath
#

Yes! We've confirmed with a few of our devices

earnest moat
#

ah sorry just saw you already mentioned that!

devout heath
#

And verified updating the android system webview was required for our dev environment to work

devout heath
earnest moat
#

so to confirm, you've already implemented each of these steps?

-adding the necessary dependency
https://developers.google.com/pay/api/android/guides/recipes/using-android-webview#add-build-dependency

-adding the necessary <queries> tags to your AndroidManifest.xml
https://developers.google.com/pay/api/android/guides/recipes/using-android-webview#add-android-manifest-queries-tags

-enabling the Payment Request API for the WebView you use in your App
https://developers.google.com/pay/api/android/guides/recipes/using-android-webview#enable-payment-request-api

#

I'd definitely recommend explicitly checking each of these, because based on the information available to us, if those have all been implemented then Google Pay should show in the ECE in a webview

#

if you've already confirmed those then we may need to get you to write in to us directly so we can debug further asynchronously

devout heath
#

Yes these are all complete, and I would assume they're fine because our dev configuration works as expected (from the android app side there is no difference)

#

I can write to you directly, where should I do that

#

Or any steps to diagnose what could be going would be useful also

earnest moat
#

I'll send a bot message now that will give you the option to write in directly to our team! if you could just include the details of your integration (Android Webview version, Google Play services version, any relevant code snippets and and any console errors you might be seeing), that'd be perfect

#

we'll have all the context from this thread as well, so don't worry about providing a very detailed description!

wraith gazelleBOT
#

Hello @devout heath, we have sent you a direct message, please check it at https://discord.com/channels/@me/1443592204038836246

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.