Franz: Cannot edit messages on Slack anymore

[Pawely]

Describe the bug
It is not possible to edit messages on slack anymore for me.

To Reproduce
Steps to reproduce the behavior:

1. Write a message on slack
2. Go to the "settings" for this message and click "Edit"
3. Message is not editable

Expected behavior
Message should be editable

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Using Franz with version: 5.4.0-beta.3

Additional context
Add any other context about the problem here.

[rmeffan]

This just happened to me with the OS X client. Edits still work fine from the same account in the iOS app.

I think it's an issue where there's an edit in progress, but Slack won't tell you where it is. We have dozens of channels (dozens!), so I'm apparently going to have to open every message from the past 24 hours to see if I can find the edit. If that doesn't work, will try nuking prefs, and then give up and try uninstalling / reinstalling.

Bloody annoying stupid bug. If an app is only going to allow a single edit, then you should make sure it's not possible for this sort of UX fail to occur.

[jeffgerickson]

I have exactly the same bug. This is only a problem on the Mac desktop app (Version 4.6.0, both production and beta); I can edit messages in the browser interface (Chrome) and on the iPad app. Even on the desktop app, the bug appears to be restricted to only one workspace.

I've tried spawning the bug in a second workspace by quitting with an unsaved edit, trying to edit more than one message at a time (which just fails silently), starting a new message while the edit is open, switching channels or workspaces while an edit is unsaved, .... all with no luck. As @rmeffan suggests, it seems like some internal busy flag has been set incorrectly.

[Langorithm]

One of my users had this problem a couple of days ago.
Check your device's time is set correctly and is synced to slack's time settings, that solved it for us.

[ableuler]

I had the same problem with the OS X client. Signing out from and re-adding the workspace fixed the problem.

[novosirj]

I ran into this recently too, and the same thing fixed it. I'm running Version 4.6.0
1bdb2ca-s@1591717570 (Production) on MacOS X 10.13.6. It appeared to be the same cause, and in fact after a reboot, when I tried to switch to a different channel, it asked me if I was prepared to give up the message I was editing. I don't remember what I answered, and it didn't ask me for a second time. There was nothing present in the "Drafts" space in Slack. Attempting to edit a message yielded nothing at all happening. Sometimes, probably if I was in the channel where that stuck message was being edited, clicking Edit would cause the channel to scroll back, but there would be nothing visible for edit.

[peteroconnor-bc]

Yep, got this bug. It persisted after quitting and re-opening slack, and even restarting the computer.

Signing out of company workspace and signing back in fixed it for me.

[peckjon]

Ditto on sign out/re-add. Thanks for the workaround!

Version 4.6.0 on OSX 10.15.5

[cotispear]

Also encountered this with v4.8.0 on macOS, confirmed that quitting/reopening did not resolve the issue, but signing out/back in to my workspace did. 🤷‍♂️

[jontucichterazo]

I just had this.
My specific case was that I was editing a pinned post and clicked on a DM to respond to that.
When I clicked back to the pinned post, selecting 'Edit' did nothing.
Signing out & in again resolved the issue.

I agree with the theory that a 'hidden draft' exists and a bug is preventing it from re-opening.

[danksim]

I had the exact same issue as @jontucichterazo on v4.8.0 today. Had to sign out and rejoin workspace.

[MichaelAroustian]

I had the exact same issue as @jontucichterazo on v4.8.0 today. Had to sign out and rejoin workspace.

same here today with version: 4.11.2

[ccooksey]

I accidentally pinned something in a DM and unpinned it. After that, I could not edit messages. Logging out of the workspace and then back in indeed fixed it.