-
Notifications
You must be signed in to change notification settings - Fork 3
chore: release 2.3.1 #608
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
base: master
Are you sure you want to change the base?
chore: release 2.3.1 #608
Changes from all commits
c522b5c
be27a0b
d700f60
9d1bd9b
8699a1f
a7c4629
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -48,7 +48,7 @@ struct SendQuickpay: View { | |
| wallet.sendAmountSats = lnurlPayData.minSendableSat | ||
|
|
||
| bolt11Invoice = try await LnurlHelper.fetchLnurlInvoice( | ||
| callbackUrl: lnurlPayData.callback, | ||
| data: lnurlPayData, | ||
| amountMsats: lnurlPayData.callbackAmountMsats() | ||
|
Comment on lines
+51
to
52
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When a fixed-amount LNURL-pay endpoint returns an invoice that fails the new core amount/metadata validation, this call now throws before Useful? React with 👍 / 👎. |
||
| ) | ||
| } else if let scannedInvoice = app.scannedLightningInvoice { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fetchLnurlInvoiceis called before thedo-catchthat toasts the error and navigates to.failure. If core validation throws (e.g.AmountMismatch), the error propagates out ofperformPayment()toSwipeButton's closure; whetherSwipeButtonsurfaces it to the user is not guaranteed. The innerdo-catchalready handles send failures with a toast + failure navigation — fetch failures should be treated the same way for consistent UX.