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.

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

'from [username]'/'to [username]' is not shown in request/send message bubble in group chat on message sender screen #2868

Closed
Serhy opened this issue Jan 2, 2018 · 2 comments · Fixed by #2947
Assignees

Comments

@Serhy
Copy link
Contributor

Serhy commented Jan 2, 2018

Type: Bug
Summary: When UserA request/send ETH in group chat from/to UserB - there is no recipient in /request (/send) message bubble is shown on the message sender screen (on UserA chat screen in this case). However, it is displayed on receiver's side (UserB in this case).

Expected behavior

'from [username]'/'to [username]' is visible in request/send ETH message bubble in group chat on sender's side

Actual behavior

'from [username]'/'to [username]' is not visible in request/send ETH message bubble in group chat on sender's side
screenshot_20180102-172752

Reproduction

  1. Open Status on UserA device
  2. Open Status on UserB device
  3. Send /faucet request by UserA (wait until you receive 0.1ETH in Wallet)
  4. UserA adds UserB in contacts
  5. UserA creates group chat with UserB
  6. In the group chat UserA taps on /request, selects UserB from the 'Request ETH' list, specifies amount and sends the message.
  7. Check message bubble on UserA screen
  8. In the group chat UserA taps on /send, selects UserB from the 'Send transaction' list, specifies valid amount of ETH (I used 0.01) and sends the message.
  9. Check message bubble on UserA screen

Additional Information

  • Status version: 0.9.10-503-g3e940b5b+ (
  • Operating System: Android 7.0 (Samsung J7 real device), iOS 11.1.2 (iPhone X)
@Serhy Serhy added the bug label Jan 2, 2018
@janherich
Copy link
Contributor

@Serhy just to be clear, this happens on develop, #2807 branch, or both ?

@Serhy
Copy link
Contributor Author

Serhy commented Jan 2, 2018

@janherich both branches affected: develop and #2807

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants