sshropshire

Hi @Hector1990 does the `GooglePayClient` get instantiated in `onCreate`? I know it's marked `lazy` in the example but the new [Activity Result API](https://developer.android.com/training/basics/intents/result) requires registration by at least `onCreate`. We...

@Hector1990 got it. Is the best way to reproduce this to turn off Wifi? Or are you seeing configuration fetches fail often?

@Hector1990 Yeah I'm trying to think of how this is possible (should lead to a potential fix if we need it). But fundamentally it looks like the SDK is attempting...

Hi @Hector1990 could you provide a small demo re-creating the issue?

@Hector1990 Still looking to reproduce and I'm unable to in the Demo app, but the root cause may be because request payment is being called in `onCreate` as well. The...

@Hector1990 the culprit here seems to be lazy instantiation of the `GooglePayClient` outside of `onCreate`. Does it work when this portion of the code is moved to `onCreate`? ```kotlin GooglePayClient(this,...

As an experiment, can we try this in `onCreate`? ```kotlin // late initialization googlePayClient = GooglePayClient(this, BraintreeClient(this, "authKey")) .apply { setListener(this@GooglePayBraintreeHostActivity) } // then Handler(Looper.getMainLooper()).post { googlePayClient.requestPayment(this, googlePayRequest) } ```...

@contissi it may be specific to Google Pay here. The workaround could be removed if `tokenize` were called in response to a user action e.g. a "Google Pay" button press,...

Hi @F9F8 thanks for using the Braintree SDK for Android. Have you tried using a `singleTop` launch mode for the deep link target `Activity`?

@F9F8 thanks for the additional info. We are looking into this issue on our side. I have a feeling this may be related to Chrome Custom Tabs. We'll post back...