Skip to content

[Bug]: LN payment can take manual refresh to recognise sent successful #1929

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

Closed
catch-21 opened this issue Jun 3, 2024 · 1 comment · Fixed by #1958
Closed

[Bug]: LN payment can take manual refresh to recognise sent successful #1929

catch-21 opened this issue Jun 3, 2024 · 1 comment · Fixed by #1958
Assignees
Labels
bug Something isn't working

Comments

@catch-21
Copy link
Contributor

catch-21 commented Jun 3, 2024

Describe the bug

I made a LN payment from one Bitkit wallet to another Bitkit wallet and it not only took a long time (around 20 seconds) but the sender didn't recognise when the payment was successful, provoking me to manually refresh to find out.

Reproduce

  1. Scan LN invoice on other Bitkit wallet
  2. Swipe to pay
  3. Wait a long time for receiver to get confetti (around 20 seconds for me this time)
  4. Sender doesn't recognise payment was successful
  5. Sender needs to swipe down to refresh and see the payment was successful. No confetti seen for sender.

Screenshots / Recording

Screenrecorder-2024-06-03-10-48-41-63.2.mp4

Operating system

Android 13 TKQ1.221114.001

Bitkit version

1e714a9

Log output

No response

@catch-21 catch-21 added bug Something isn't working triage This issue needs to be looked over by the team labels Jun 3, 2024
@pwltr pwltr removed the triage This issue needs to be looked over by the team label Jun 5, 2024
@catch-21
Copy link
Contributor Author

catch-21 commented Jul 2, 2024

See #1958 (comment) for testing notes
Also not an issue in v127 or v128

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

Successfully merging a pull request may close this issue.

2 participants