Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Incorrect? Already spent from address error #1386

Closed
sloganking opened this issue Apr 24, 2019 · 3 comments · Fixed by #1835
Closed

Incorrect? Already spent from address error #1386

sloganking opened this issue Apr 24, 2019 · 3 comments · Fixed by #1835
Assignees
Labels
C - Shared L - Need to reproduce Lifecycle - Need to reproduce this issue T - Bug Type - Bug: Something isn't working

Comments

@sloganking
Copy link

Bug description

  • Trinity reports unspent address as spent when re-attaching transaction.
  • Trinity attempts to "retry" this transaction forever, even after confirmation.

Possibly related issue

#1036

Environment Specs

What device are you running Trinity on?

  • Manufacturer: Samsung
  • Model: Galaxy S8+
  • OS version: Android 9

What build of Trinity are you running? Please provide the full version (you can find it in Settings > About Trinity).

  • Trinity version: 0.6.2 (55)

Steps To Reproduce

  1. get network error when generating receiving address but still receive address
  2. send funds to generated address from same account
  3. Error

Expected behavior

The wallet should not tell the user that an unspent address is already spent

Actual behavior

Trinity tells users that the sending address has already been sent from, yet broadcasts the transaction in question (possibly unsafe)

Errors

1
2
3
4
5

@laumair laumair self-assigned this Apr 25, 2019
@laumair laumair added C - Mobile C - Shared L - Need to reproduce Lifecycle - Need to reproduce this issue labels Apr 25, 2019
@sloganking
Copy link
Author

Still ongoing in Trinity V 0.7.0 (59)

@laumair
Copy link
Contributor

laumair commented Apr 30, 2019

@SleepingFox88 I cannot seem to reproduce this issue.

What notification did you see after you retried the failed transaction for the first time in history?

@sloganking
Copy link
Author

Has this issue been fixed?

I see #1607 marked this issue as a duplicate and is now closed.
Also #1644 marked this issue as closed and has been merged.

I updated mobile trinity to v0.7.2(67) and after an initial "Address already spend from" error message, the problem seems to be fixed for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C - Shared L - Need to reproduce Lifecycle - Need to reproduce this issue T - Bug Type - Bug: Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants