T2716
In the case of a burn token tx that burns all of a token balance, the useEffect loop that unlocks the UI was not being hit. Add a simple conditional which catches this case.
Details
Details
- Reviewers
emack - Group Reviewers
Restricted Project - Commits
- rABCfc4d566a78df: [Cashtab] Patch issue with burn all of a token locking UI
npm start
Burn all of a token and note that UI unlocks at same time app redirects to home
Burn some of a token and observe UI unlock functions as expected
Send some of a token and observe UI unlock functions as expected
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- fix-etoken-burn-lock
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 20374 Build 40421: Build Diff cashtab-tests Build 40420: arc lint + arc unit
Event Timeline
Comment Actions
The full token balance burn issue is resolved however I noticed an edge case where sending etokens to the same etoken address it is being sent from will trigger a similar continuous loading process, however in this case it doesn't send it at all. This is reproducible in prod as well.
Comment Actions
I've created T2719 to handle this. If this issue currently exists at cashtab.com and is not introduced by this diff, then it should be resolved in its own diff.