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

Migeration & Crash Issue #80

Closed
rahmanprofile opened this issue Jun 12, 2023 · 2 comments
Closed

Migeration & Crash Issue #80

rahmanprofile opened this issue Jun 12, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@rahmanprofile
Copy link

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behaviour:

  1. Enter VPA
  2. Trigger payment
  3. Go to opened UPI app
  4. ...
  5. **``` Flutter
    The plugin upi_pay uses a deprecated version of the Android embedding.
    To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
    If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

### Expected behaviour
A clear and concise description of what you expected to happen.

### Screenshots
If applicable, add screenshots to help explain your problem.

### Environmental Details
- OS: [e.g. Android 11]
- Device: [e.g. OnePlus Nord]
- Package Version: [e.g. v1.0.0]
- UPI Applications in the device: [e.g. - GPay, Paytm]
- Play Store: [e.g. Google, Mi, Vivo]
- Other UPI / Payment packages used in the app: [e.g. - razorpay_flutter]

### Additional context
Add any other context about the problem here.
@rahmanprofile rahmanprofile added the bug Something isn't working label Jun 12, 2023
@rahmanprofile
Copy link
Author

Through the software going to crash help or solve this issue as soon as possible : )

@drenther
Copy link
Owner

Duplicate of #79

@drenther drenther closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants