sshropshire
sshropshire
Hi @pier1287 thanks for your patience. We've notified Cardinal once again and we're waiting to hear back on next steps.
@dcampogiani no worries. We appreciate all feedback, especially if we can forward it to Cardinal.
Hi @SirLordPouya thanks for adding feedback. Cardinal has acknowledged the issue and is working on a set of next steps.
Hi @auxDK thanks for using the Braintree SDK for Android. I've notified Cardinal, our 3rd Party MPI Provider of this issue, and we'll report back here with updates once we...
@idomo1 thanks for using the Braintree SDK for Android. I checked the source and you're correct. We'll investigate and provide a fix as soon as we can.
@idomo1 this will be in the next release. Thanks for the feedback here!
@idomo1 we don't have an exact ETA. There are some updates to the Core library that we would also like to get in. In the meantime, the [SNAPSHOT](https://github.com/braintree/braintree-android-drop-in#adding-it-to-your-project) build is...
Hi @v-sulimov thanks for using the Braintree SDK for Android. In the repro steps, we return to the Android home screen and then launch the `Braintree` demo app using the...
@v-sulimov yes selecting the app from the launcher screen will cause Android to launch the activity with category `android.intent.category.LAUNCHER` (specified in AndroidManifest.xml). Since the application is already running, it pops...
@v-sulimov this exists in the `3.x` version as well. It is easier to recover from a user perspective though, since the CCT is launched as a separate task. This has...