tomer8007 / whatsapp-web-incognito

A Chrome extension that disables read receipts and presence updates on WhatsApp Web
MIT License
318 stars 75 forks source link

Messages not loading with error: "Waiting for this message. This may take a while" #76

Closed chronos000 closed 2 years ago

chronos000 commented 2 years ago

Every now and then (approximately once a week), all new messages stop showing on web.whatsapp.com. Instead, the text of these new messages show "Waiting for this message. This may take a while" . There is also a "learn more" link, with possibly related information.

image

I tried reloading web.whatsapp.com, but the problem persists. Even if I disable WAIncognito extension and reload the site, it still does not load new messages.

The only way I found to correct the problem is to completely logout from whatsappweb, and re-link the device once again.

I got into the multi-device program, and unfortunately I can't leave it to test if that has something to do with this.

Let me know if I can provide any logs or debug info.

tomer8007 commented 2 years ago

I've seen such an issue in the past, but can't remember exactly what triggered it. I think this can happen if the extension messes up with incoming messages. I would try to

  1. See if this is related to the message restore feature by trying to disable it
  2. Look for javascript errors in the console
chronos000 commented 2 years ago

I've seen such an issue in the past, but can't remember exactly what triggered it. I think this can happen if the extension messes up with incoming messages. I would try to

  1. See if this is related to the message restore feature by trying to disable it

I forgot to mention that this was the first thing I tried. Disabling the restore feature and reloding the site did not solve the problem.

  1. Look for javascript errors in the console

I'll do this next time the problem appears

Would something like this output be ok? image

Let me know if you would prefer any other way to export the data, or if you need any other information.

tomer8007 commented 2 years ago

OK, looks like we have the problem. Will try to fix it next week.

EDIT: @chronos000 The error above seems to be unrelated and I couldn't reproduce it, can you provide a diffrent one, or can you receive newer messages after the "Waiting for this message" text shows up?

tizosa commented 2 years ago

image "Missing Signed..." only appears after that problem happen. Edit: Started to show again on another client. I can confirm that they are linked.

tomer8007 commented 2 years ago

@tizosa Thank you, this has to be a result of a corruption in the signal DB. Until I'll find the real cause the relevant logic is now disabled (f9bceb9915c957634c2c88d020da4095606f8180).

tomer8007 commented 2 years ago

@tizosa @chronos000 Does it still happen for you since version 1.8.5?

RezqZiyad commented 2 years ago

@tizosa @chronos000 Does it still happen for you since version 1.8.5?

No, it doesn't!

chronos000 commented 2 years ago

@tizosa @chronos000 Does it still happen for you since version 1.8.5?

I have disabled multi-device in whatsapp because I didn't want to loose WAIncognito's habitlity to recovery deleted messages.

tomer8007 commented 2 years ago

the relevant logic is now disabled (https://github.com/tomer8007/whatsapp-web-incognito/commit/f9bceb9915c957634c2c88d020da4095606f8180).

Message restore feature is enabled again in v1.8.6 for multi-device.

chronos000 commented 2 years ago

the relevant logic is now disabled (f9bceb9).

Message restore feature is enabled again in v1.8.6 for multi-device.

The good news is that now deleted messages do not corrupt the database. The bad news is that instead of restoring the messages, now the deleted messages show "failed to restore message"

tomer8007 commented 2 years ago

@chronos000 Uhh Is it happening also for messages that were deleted after you updated to 1.8.6?

FieryRMS commented 2 years ago

@chronos000 Uhh Is it happening also for messages that were deleted after you updated to 1.8.6?

I am on 1.8.7, but the issue persists. Here is the error log, image

The message that was deleted was by me in a group chat which i deleted from the phone.

chronos000 commented 2 years ago

@chronos000 Uhh Is it happening also for messages that were deleted after you updated to 1.8.6?

I am on 1.8.7, but the issue persists. Here is the error log, image

The message that was deleted was by me in a group chat which i deleted from the phone.

I am experiencing the same behaviour

tomer8007 commented 2 years ago

@chronos000 @FieryRMS Still happening on 1.8.8?

FieryRMS commented 2 years ago

@tomer8007 Yes the issue still persists. This is a screenshot just after refreshing the page with the update. The first error is from sending a message, the next one is from deleting it. The message was sent and deleted from my phone. image

tomer8007 commented 2 years ago

@FieryRMS After the page finishes to load, is SenderKeyMessage defined? Also, do you still see the "Failed to restore message" for new messages?

FieryRMS commented 2 years ago

@tomer8007 Where do I check if it's defined? I sent the message from my phone after the page had loaded completely and even then the error was thrown. No it doesn't show "Failed to restore message" anymore for deleted messages. It shows Whatsapp's "You deleted this message".

FieryRMS commented 2 years ago

@tomer8007 I did a search on your repo for definitions for SenderKeyMessage and it seems to defined in core/parsing/.protobuf/WhisperTextProtocol.js, this file seems to be missing on my end, perhaps this could be the reason?

image This location doesn't exist on my end, image

tomer8007 commented 2 years ago

Yes, this is the case here. I would guess this is because of the dot-folder .protobuf that's being ignored by your computer somehow? How did you even load the extension?

FieryRMS commented 2 years ago

@tomer8007 I had updated the extension to 1.8.8 through chrome before. Now, I disabled the chrome version, and installed the 1.8.8 version from your repo. The .protobuf folder was present this time, and the extension was working as intended, the deleted messages was being saved.

Perhaps its a chrome issue? Perhaps they are the ones ignoring .folders?

tomer8007 commented 2 years ago

@FieryRMS Yes, this is apparently the case, and it's also an issue that I would probably never reproduce otherwise (so thank you). Please try version 1.8.9 (2fe930ba8d590910aaf38af30ea937f0ba54b040) from the store.

FieryRMS commented 2 years ago

@tomer8007 no problem!! And yes, now its working even from the store!