Status-react: "Resend" option doesn't resend message on Android

Created on 14 Oct 2019  路  10Comments  路  Source: status-im/status-react

Bug Report

Problem

"Resend" option doesn't work on android devices (tried on LG V20, Android 8).
Also popup is not closed when tapping on the blurred area.

Expected behavior

can resend message

Actual behavior

photo_2019-10-14 16 27 18 jpeg 2019-10-14 16-27-31

Reproduction

A bit complicated to emulate this behavior if you have strong connection and fast device.
Below are steps that working for me.

  • Open Status
  • Join public chat
  • Go offline
  • Go online and quickly until "Connecting" is shown send message
  • Turn off WI-FI
  • Wait ~1 min
  • Turn on WI-FI and after a while you can see "Not confirmed. Tap for options."
  • Tap on it, try to resend message

Additional Information

  • Status version: nightly 14/10/2019
  • Operating System: Android

Logs

Full logcat:
resend_button.log

10-14 16:20:34.652 30863 30901 D ReactNativeJS: DEBUG [status-im.utils.handlers:32] - Handling re-frame event:  :signals/signal-received
10-14 16:20:34.661 30863 30901 D ReactNativeJS: DEBUG [status-im.events:667] - :event-str {"type":"wallet","event":{"type":"newblock","blockNumber":8739634,"accounts":[]}}
10-14 16:20:41.407 30863 30901 D ReactNativeJS: DEBUG [status-im.utils.handlers:32] - Handling re-frame event:  :chat.ui/set-chat-ui-props
10-14 16:20:42.167 30863 30901 D ReactNativeJS: DEBUG [status-im.utils.handlers:32] - Handling re-frame event:  :chat.ui/set-chat-ui-props
10-14 16:20:45.605 30863 30901 D ReactNativeJS: DEBUG [status-im.utils.handlers:32] - Handling re-frame event:  :signals/signal-received
10-14 16:20:45.615 30863 30901 D ReactNativeJS: DEBUG [status-im.events:667] - :event-str {"type":"wallet","event":{"type":"newblock","blockNumber":8739635,"accounts":[]}}
10-14 16:20:54.351 30863 30901 D ReactNativeJS: DEBUG [status-im.utils.handlers:32] - Handling re-frame event:  :signals/signal-received
10-14 16:20:54.361 30863 30901 D ReactNativeJS: DEBUG [status-im.events:667] - :event-str {"type":"wallet","event":{"type":"newblock","blockNumber":8739636,"accounts":[]}}
android bug

All 10 comments

@churik I tried to replicate on android emulator, and an huawei media pad, but in both cases it worked as expected, would you mind trying to replicate once more? seems more like a UI bug to me, does deleting a chat work ? (the one that uses the same pop-up). Thanks!

I have tried to install nightly on a moto g5 , but I can't install status anymore on there (says This app could not be installed), maybe something changed with the build? (any idea @jakubgs @PombeirP ?)

@cammellos yes, deleting is working fine.
Unfortunately, I have only one device, where I can replicate it.
@Serhy please help

Yes, I reproduced on my devices (Android 6.0.1, Android 8, Android 9)
So as described in the steps, first you need to get 'Not confirmed. Tap for options' under message.
(I've got it catching 'Send' button active while WiFi disabled)
Now, if you stay Offline with Not confirmed state under message - tapping upon this option has no issues when Resend/Delete and tapping anywhere on screen closes this bottom-pop up.

However, after you appear online (note: the status of chat at the top changes from Offline -> Connecting... -> Connected which may screw UI why issue appears) then this bug happens:
tapping anwhere on shadowed area and area of 'Resend' button have no effect, - instead chat items are selectable (so if I tap upon 'Resend' which is above another user-pic with message - I can open user profile).

Also, if to reopen app that UI glitch still takes place. The 'Delete message' works though (maybe because this option appears above not the chat with messages view but 'Chat input'.

Basically yes, this Resend/Delete message dialog with shadowed area appears to have no effect in the messages area of chat view, after user appears online.

I can record video of what happens with logcat if needed.

Just to make sure, did you use the latest nightly?

Just to make sure, did you use the latest nightly?

Yes, 0.14.0 (2019101602) nightly build.

ok, replicated by waiting to come back online, thanks!

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work has been started__.

These users each claimed they can complete the work by 3聽weeks, 3聽days from now.
Please review their action plans below:

1) tbenr has been approved to start work.

I already found the cause and fixed in a PR :)
2) tkembo has applied to start work _(Funders only: approve worker | reject worker)_.

I have to first troubleshoot through but I'm sure I can figure out what the issue is and fix it

Learn more on the Gitcoin Issue Details page.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work for 90.0 DAI (90.0 USD @ $1.0/DAI) has been submitted by__:

  1. @tbenr

@StatusSceptre please take a look at the submitted work:

  • PR by @tbenr

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__The funding of 90.0 DAI (90.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @tbenr.__

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lukaszfryc picture lukaszfryc  路  117Comments

flexsurfer picture flexsurfer  路  42Comments

jakubgs picture jakubgs  路  174Comments

flexsurfer picture flexsurfer  路  57Comments

jeluard picture jeluard  路  68Comments