Clicking "resend message" on a message that failed to send makes it disappear

(#10) Bug Closed: Fixed messaging

Reproduction steps

  1. Send a message but have it fail to send
  2. Click resend button on it

Observed behaviour

It disappeared Expected behaviour Should appear again in the chat screen as if it were a message I had just typed and was in the process of getting sent

Details

Summary

As we all know the fluxer.app server is currently falling over so when I tried to send a message it didn't make it through. That's fine, the message reappeared in the chat screen with a "resend" button on it. But when I clicked the button, the message disappeared. It also did legitimately try to resend in the background, but when that failed a second time the unsent message was gone and I couldn't just click again to resend.

Area

Frontend / Web

Environment

fluxer.app right now?

6 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote edited
Status changed from Fixed to Awaiting confirmation
This may be fixed in the current version. If it still happens for you, please say so here.
Comment by Rex
RexSystem 1 vote
Status changed from Awaiting confirmation to Fixed
Imported from GitHub, fix shipped. Closed in bulk.
Comment by @Pandooroo
RexSystem 1 vote originally by @Pandooroo on GitHub
Same issue here - on either Web or the Windows app, sending messages don't work for me and when trying to resend them, it disappears.
Comment by @AstralPhnx
RexSystem 1 vote originally by @AstralPhnx on GitHub
I think this one is fixed now? Can we verify?
Comment by @aikaterna
RexSystem 1 vote originally by @aikaterna on GitHub
I had a message send time out within the last 30 minutes before this post and I was able to hit the button to resend it without the message disappearing.
Comment by @AstralPhnx
RexSystem 1 vote originally by @AstralPhnx on GitHub
I had a message send time out within the last 30 minutes before this post and I was able to hit the button to resend it without the message disappearing.
Alright, I can also confirm this new behaviour. If we get a few more confirms then this can probably be closed