search

minibits-cash / minibits_wallet

MIT License
74 stars 7 forks source link

Issue when making LN payment #27

Closed Erojo closed 9 months ago

Erojo commented 11 months ago

Having updated the app to the latest version (2023-12-15), an error occurs every time I try to make an LN payment. See the attached images:

1

2

minibits-cash commented 11 months ago

Thanks for reporting the issue. Please give me the exact version you are running from Developer settings.

Will work on it this evening.

minibits-cash commented 11 months ago

As a first quick attempt please try to send (Share ecash) and if token is generated, copy it and receive by pasting back to the wallet.

Notify here if it passed through.

Erojo commented 11 months ago

Sure, this is the version I'm running:

4

Erojo commented 11 months ago

As a first quick attempt please try to send (Share ecash) and if token is generated, copy it and receive by pasting back to the wallet.

Notify here if it passed through.

I tried what you say and got the same error message when generating the ecash token. I've got two mints and It happened the same thing in both of them.

minibits-cash commented 11 months ago

There is an update ready for you: v0.1.5-beta.18.

  1. As a first step after update, check on the Manage mints screen Recovery indexes for each mint (tap on the mint, shown on the bottom of the modal). Check if they are "undefined" or hold a numeric amount - just write it here for root cause analysis purpose.
  2. Then please be so kind and for the duration of the test check that logging in Settings > Privacy is on and set Log level to Debug in Developer options. After the test, turn the level back to Error default.
  3. Then, please go to Settings > Backup and recovery > Recovery tool (under local backup switch) and select one of the backed up proofs in "Unspent" category. Remember from which mint it is based on keyset "id" - for Minibits mint it is 9mlfd... and the amount. Bigger proof amount the better. Then re-try to send to yourself exact same amount from the same mint. You should be able to show exported token (as such tx does not involve split with the mint). Copy token and try to receive it (this involves split everytime). Write if receive failed again. Re-check the recovery index for the mint and write if it changed.
  4. If receive failed, review rough number of transactions in your history (order of magnitude is enough - single, dozens, hundred?) Then go to Settings > Backup and recovery > Increase recovery indexes. Depending on the wallet history (number of past transactions), tap on Increase - it increases the indexes by 50, increase to get safely over your tx number.
  5. Repeat point 3 and write results

Sorry for many steps involved, but unfortunately I can not simulate the error myself, I encountered it only during early development of seed based recovery when it was cused by a bug in cashu-ts library that was immediately fixed.

Erojo commented 11 months ago

I have managed to make a LN payment. The steps I took were: Updated the app as you suggested Checked that the recovery indexes for both mints were undefined Went to the "Backup" menu, and 1) Remove spent ecash and 2) Increase recovery indexes

Now in the "Manage mints" menu, both mints have a numerical recovery index.

Sorry for the inconvenience. Thanks for your help.

El sáb, 16 dic 2023 a las 22:44, minibits-cash @.***>) escribió:

There is an update ready for you: v0.1.5-beta.18.

  1. As a first step after update, check on the Manage mints screen Recovery indexes for each mint (tap on the mint, shown on the bottom of the modal). Check if they are "undefined" or hold a numeric amount - just write it here for root cause analysis purpose.
  2. Then please be so kind and for the duration of the test check that logging in Settings > Privacy is on and set Log level to Debug in Developer options. After the test, turn the level back to Error default.
  3. Then, please go to Settings > Backup and recovery > Recovery tool (under local backup switch) and select one of the backed up proofs in "Unspent" category. Remember from which mint it is based on keyset "id" - for Minibits mint it is 9mlfd... and the amount. Bigger proof amount the better. Then re-try to send to yourself exact same amount from the same mint. You should be able to show exported token (as such tx does not involve split with the mint). Copy token and try to receive it (this involves split everytime). Write if receive failed again. Re-check the recovery index for the mint and write if it changed.
  4. If receive failed, review rough number of transactions in your history (order of magnitude is enough - single, dozens, hundred?) Then go to Settings > Backup and recovery > Increase recovery indexes. Depending on the wallet history (number of past transactions), tap on Increase - it increases the indexes by 50, increase to get safely over your tx number.
  5. Repeat point 3 and write results

Sorry for many steps involved, but unfortunately I can not simulate the error myself, I encountered it only during early development of seed based recovery when it was cused by a bug in cashu-ts library that was immediately fixed.

— Reply to this email directly, view it on GitHub https://github.com/minibits-cash/minibits_wallet/issues/27#issuecomment-1858936372, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNB5JC6AM3ZKLCOUCQLT6DYJYI3XAVCNFSM6AAAAABAXRWFJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHEZTMMZXGI . You are receiving this because you authored the thread.Message ID: @.***>

-- Eñaut Rojo

minibits-cash commented 11 months ago

Good to hear. Did the removal of spent ecash end with finding something? It prints out number of spent proofs.

No inconvenience, it is a bug that should not happen, just a rare one, where we need to figure out the conditions making it occur.

Thanks for your help.

minibits-cash commented 9 months ago

Known room for occurrence of this bug has been eliminated in recent v0.1.6-beta release.