Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When calling initPaymentSheet with the customFlow flag again, the application hangs #1962

Open
kirill09 opened this issue Oct 15, 2024 · 1 comment
Assignees
Labels
Android Issue related to Android native bindings bug Something isn't working

Comments

@kirill09
Copy link

When calling initPaymentSheet with the customFlow flag again, the application hangs

Steps to reproduce the behavior:
In the example, the following steps need to be done.

  1. Custom Flow
  2. Init payment sheet
  3. Select payment method
  4. Add card 4242 4242 4242 4242(does not matter)
  5. Pay now
    We receive a successful payment.
  6. Init payment sheet
    Stripe.instance.initPaymentSheet method does not complete its work.

Stripe.instance.initPaymentSheet method completed successfully

  • OS: Android 14
  • Package version: 11.2.0
  • Flutter version: 3.24.2
flutter-stripe.mp4

An exception is raised that is not handled anywhere.
com/stripe/android/paymentsheet/repositories/ElementsSessionRepository.kt:58
Failure(kotlinx.coroutines.JobCancellationException: Job was cancelled; job=SupervisorJobImpl{Cancelling}@30f3594)

@kirill09 kirill09 added the needs triage Needs triage label Oct 15, 2024
@remonh87
Copy link
Member

@jonasbark I can reproduce this issue can you check if it is something in the Android factory?

@remonh87 remonh87 added bug Something isn't working Android Issue related to Android native bindings and removed needs triage Needs triage labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Android Issue related to Android native bindings bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants