#Edi-gpay-expo

1 messages · Page 1 of 1 (latest)

static plover
#

Hey there, you using our React Native library?

pine lotus
#

Hi, yes, I'm currently locked to 0.6.1 (due to Expo 45), but also tried 0.12.0 (latest), and the same thing happens.

static plover
pine lotus
#

I've already done that, but in order to integrate with my android app, as they request

#

I'm asked to provide a screenshot of the flow.

#

And I'm not able to get those ... since it gives me an error.

static plover
#

In test mode?

pine lotus
#

Yes ..

#

This is the code, taken from Stripe's example.

#

I am creating the paymentintend clientsecret with the stripe test keys as well

static plover
#

Are you correctly initialising Google Pay in the app config?

pine lotus
#

"app config"?

static plover
#
<meta-data
    android:name="com.google.android.gms.wallet.api.enabled"
    android:value="true" />
pine lotus
#

it's react native, not android android

#

i think this only has to do with bare workflows though ..

#

let me try and check

static plover
#

Yup, but you should still have an AndroidManifest file. That example above is RN

pine lotus
#

Yeah, 1 min, i can try

static plover
#

@pine lotus Did that help?

pine lotus
#

No, it didn't

#

But I am checking something else

#

I already had that there, it's automatically added when you use expo managed workflow

#

I've forgot to add testEnv: true to initGooglePay

#

So, I'm making a new build, for the app to check if that sorts it.

static plover
#

Ah, yep. testEnv: false will require your app to be registered with Google

pine lotus
#

Yep, that sorted it 🙂

#

You can archive this,