Closed ReedCent closed 2 months ago
I wasn't able to replicate this :thinking: sometimes this sort of thing happens w/ facebook changing their algos, but in this case (on my end) it all looks the same. I'm a few versions of chrome behind though so i can maybe try that angle?
as it is otherwise, logs and stuff look fine. Which is actually even more surprising, something usually breaks or throws an explicit error
I'm a few versions of chrome behind though so i can maybe try that angle?
What version of Chrome are you on? Maybe I can try downgrading
I can confirm I am facing same issue after updating my browser to latest as I can see in updated browser messenger UI was changed recently.
Got it. Might be that. I'm on chrome 121, but I can try updating and seeing if that fixes it. Thanks a ton @dollaruw for the added information!
Okay so I've been looking around and I don't actually know how to downgrade Google Chrome and it seems I can't figure it out. The best lead I got was this which still didn't work with me: https://stackoverflow.com/questions/54927496/how-to-download-older-versions-of-chrome-from-a-google-official-site
How are things working on your end? Did updating Chrome manage to reproduce the issue?
Actually no, so I'm not sure it's a chrome version thing. This may be a messenger AB test that I'm just not part of yet, or it could be an OS thing (generally unlikely? but im on ubuntu so maybe?)
This makes it a bit hard for me to fix anything :cry: As of right now I can't easily figure out what UI elements actually changed --> i can't update the code to push the right buttons
I am on mac OS and on a older version of Brave browser which is based on Chromium v123. Now It unsent messages but misses few messages also sometimes unsent same message twice. Also sometime process got killed without removing all messages.
If you are not getting UI then you can try changing your browsers useragent to Mac OS browser and try.
So, after reinstalling Chrome, it finally worked. I also deactivated, reactivated and relogged in on my account but I doubt that affects anything.
However, similar to @dollaruw's case, it doesn't work optimally. Messages are either skipped without being unsent or unsent and then deleted from your end. Between the end of every message batch, there is a 50/50 chance wherein it either continues to the next batch flawlessly or it will misposition the selection and it'll target a message not in the right order, thus skipping some messages, or it'll target a message already unsent, thus unsending it twice. This can also affect the recipient's messages and accidentally removing their messages too.
Have not encountered process getting killed, though. Maybe it's because I haven't tested/waited long enough.
ok that weirdness i was able to also experience, and can likely try and fix that
gonna merge this into #119
Describe the bug Whenever I press "Remove Messages", nothing happens.
To Reproduce Steps to reproduce the behavior:
Expected behavior For messages to start being unsended.
Screenshots
Desktop (please complete the following information):
Logs www.messenger.com-1717815183284.txt
Misc I've already tried to unsend one message as you can see at the very latest message and it seems to be possible to unsend for this chain. Edit: I've also already tried to use the extension both from the Webstore and as a clone from here.