sshropshire

@sdoward I want to say thanks for your time as well. This is some of the best feedback we've gotten so far. We want to offer the best developer experience...

@sdoward like @sarahkoop mentioned we have a proposed solution that may address some of your concerns and we're gathering feedback to make sure we're headed in the right direction. And...

@mikkoville the PayPal flow is designed to only deliver a "canceled" event once (on first access). After that, the browser switching context remains dormant until the user is able to...

@mikkoville correct yes. We store some metadata in encrypted shared prefs to protect payment flows from being interrupted by process kills. Looking again at the provided code snippet though, I...

@mikkoville the best way in this case would be in response to some user action. I understand there may be edge cases though and if we need to look into...

Hey @mikkoville touching base. Any luck with the proposed workaround?

@mikkoville definitely yes. It's technically in beta at the moment but we won't be introducing any breaking changes in this current major version. We coordinate directly with the native checkout...

@mikkoville @aligokdemir our [Native Checkout module for PayPal](https://developer.paypal.com/braintree/docs/guides/paypal/native-checkout/android/v4) is in beta. It uses an activity instead of switching to a browser. This takes Chrome Custom Tabs out of the equation....

> This happens when users previous try is broken by activity death due to low device resources or similar situation and the cancelled event is not cleared from BraintreeClient. So...

@soarb this is now released in version [6.4.0](https://github.com/braintree/braintree-android-drop-in/blob/master/CHANGELOG.md#640). If you have additional concerns, feel free to open another issue and we'll take a look. We are also tracking the visual...