Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This fixes #2821.
Before, we were using
lnurl.minSendable
foramount
only, but it's needed forsatAmount
also, since this is actually used for sending (amount
is only used for displaying).Additionally fixed another bug: When unit was set to
₿
orFiat
when scanning the lnurlp QR,lnurl.minSendable
was used without conversion, resulting in₿ 1
or$1
.Note: In
Fiat
case it will display$0.00
in Amount input now, which is correct, but also₿0.00 000 000
and0sats
, which is wrong, because this conversion here uses the actual input$0.00
. It still uses the correct satAmount (1) internally, so when user proceeds it works fine (see last screenshot), but of course we should think about how to handle this better, but not in this PR.It still uses

1sat
, although displayed Amount was converted to0sats
in the view before:This pull request is categorized as a:
Checklist
yarn run tsc
and made sure my code compiles correctlyyarn run lint
and made sure my code didn’t contain any problematic patternsyarn run prettier
and made sure my code is formatted correctlyyarn run test
and made sure all of the tests passTesting
If you modified or added a utility file, did you add new unit tests?
I have tested this PR on the following platforms (please specify OS version and phone model/VM):
I have tested this PR with the following types of nodes (please specify node version and API version where appropriate):
Locales
Third Party Dependencies and Packages
yarn
after this PR is merged inpackage.json
andyarn.lock
have been properly updatedOther: