-
Notifications
You must be signed in to change notification settings - Fork 984
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
bug #4876 - cleaning up failed transactions and added stricter check … #4885
Conversation
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.
👍
branch PR-4885: |
Exact steps:
02:38 E/ReactNativeJS: Error: Doesn't support name: |
90% of end-end tests have passed
Failed tests (3)Click to expand
Passed tests (26)Click to expand
|
d7e29ba
to
d0afb49
Compare
branch PR-4885: |
82% of end-end tests have passed
Failed tests (5)Click to expand
Passed tests (23)Click to expand
|
…ded stricter check for chat wallet onboarding Signed-off-by: Julien Eluard <[email protected]>
d0afb49
to
ac2780e
Compare
fixes #4876
Summary:
We check if there is a current transaction when we do wallet onboarding because it tells us the difference between wallet onboarding directly vs onboarding triggered by
/send
commands. The cause of the problem was that failed transactions were not cleaned up and remained "current", which means that if the user did have a failed transaction before finishing onboarding, we'd get this errorThe solution in this PR is to clean up the current transaction when failed and also to add more defensive checks in onboarding, just in case.
EDIT: This PR now also marks successful transactions as not in progress and not from chat any more (if they were). This should prevent them from triggering the same behavior as the one with failed ones described above.
Steps to test:
see #4876
status: ready