Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Incoming transactions in 1-1 chat doesn't change status to 'Confirmed' if sender was keycard account #10905

Closed
churik opened this issue Jul 2, 2020 · 1 comment · Fixed by #10906
Closed

Incoming transactions in 1-1 chat doesn't change status to 'Confirmed' if sender was keycard account #10905

churik opened this issue Jul 2, 2020 · 1 comment · Fixed by #10906

Comments

@churik
Copy link
Member

churik commented Jul 2, 2020 •
edited
Loading

Bug Report

Problem

follow #10893 (comment) - reproduced in PR.
Transaction sender is this case - keycard account

Expected behavior

'Confirmed' state for recipient

Actual behavior

End state for user B below
IMAGE 2020-07-02 14:57:47

Reproduction

  • User A sends address request to user B
  • User B sees request and accepts
  • User A sees request is accepted and signs and sends transaction
  • User B continues to see Shared Status account (2h later) even though on tx History the transaction shows as received.

Additional Information

  • Status version: nightly 02/07/2020
  • Operating System: Android, iOS

Logs

Full logcat:
full-logcat.log
Status log before relogin:
Status-debug-logs.zip
Status log after relogin (issue is still preserved):
Status-debug-logs.zip

Transaction ID: 0x6537c3c2582a6d7ceab10a5a7c25f6ccef12204c5e0a0e482975fb440894d0e4
@churik churik added bug labels Jul 2, 2020
@churik churik changed the title Sometimes incoming transactions in 1-1 chat doesn't change status to 'Confirmed' Incoming transactions in 1-1 chat doesn't change status to 'Confirmed' if sender was keycard account Jul 2, 2020
@churik
Copy link
Member Author

churik commented Jul 2, 2020

Consequence of #10882 (comment)

@churik churik mentioned this issue Jul 3, 2020
Merged
@weekly-digest weekly-digest bot mentioned this issue Jul 5, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[keycard] Fix assets message signature status-im/status-mobile
1 participant
@churik