Hector

I think this can be reproduced by: 1. Complete the payment in paypal page, don't back to the app by deeplink. 2. Return to their app by switching manually.

I provided the video here: https://github.com/braintree/braintree_android/issues/611

@sarahkoop Hi, I skip some business logic codes. ``` class GooglePayBraintreeHostActivity : BraintreeHostActivity(), GooglePayListener { @VisibleForTesting internal val googlePayClient: GooglePayClient by lazy { GooglePayClient(this, BraintreeClient(this, "authKey")) .apply { setListener(this@GooglePayBraintreeHostActivity) }...

Hi @sshropshire Yes, the `startPaymentRequest ` is executed in `onCreate`. So the `GooglePayClient` gets instantiated in onCreate. And the crash doesn't happen all the time, only when failing on getting...

@sshropshire Maybe you can use a sandbox tokenization in product env. I can reproduce it in this way.

Hi @sshropshire , is there any update about this issue?

Hi @sshropshire, a new hint. Whenever I first launch Google Pay firstly, it works fine. But then I canceled the payment; then I wanted to relaunch it, and it crashed....

Hi @sshropshire, is there any update about this issue? We got more crashes in the production. ``` Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.activity.result.ActivityResultLauncher.launch(java.lang.Object)' on a null...

@sshropshire Hi, is there any update for this issue? If not, I will revert our Google Pay implementation to the previous version.

@sshropshire Hi, the lazy instantiation of the `GooglePayClient` is inside of `onCreate`. Now it's initialized in `startPaymentRequest `, and `startPaymentRequest ` is called in `onCreate`. ``` override fun onCreate(savedInstanceState: Bundle?)...