Joke Collection Website - Public benefit messages - Has the delay in WeChat messages been resolved in iOS 14?

Has the delay in WeChat messages been resolved in iOS 14?

With the release of iOS14, many people are concerned about WeChat. So, has the bug of delayed WeChat messages in iOS14 been fixed? According to reports from many netizens, after updating to the iOS14 version, WeChat messages cannot be withdrawn. How to solve this problem? Next, let’s take a look! Has the WeChat message delay in iOS 14 been resolved?

The WeChat message delay is not a bug, it is a problem with Apple’s push mechanism and cannot be corrected.

Some netizens said that the delay of WeChat has been much smaller recently. I wonder if the problem is caused by updating the WeChat version. You can also uninstall WeChat and reinstall it. What should I do if WeChat messages cannot be withdrawn in iOS 14?

A bug has been discovered: WeChat messages cannot be withdrawn

Netizens said that the message can be withdrawn by long pressing with two fingers and swiping right, so this is not a BUG. The method of operation is a little different from before.

Some netizens reported that I gradually no longer have any expectations for iOS updates. They are all slight modifications in form, without substantial changes, and they insist on periodic forced updates. Maybe domestic machines are like this too? I don’t know much about it, but the act itself is quite boring. There is a sense of presence if you watch it too much, but it loses its value. Whose problem is the delay in the iOS version of WeChat?

This is WeChat’s problem, because in addition to ios, other platforms will also have it.

This is also why the phone sleeps because it doesn't happen as long as the phone doesn't lock the screen.

It has nothing to do with ios version and nothing to do with router dns, I have tested it.

Reason: The WeChat client must accept all information (WeChat personal information, WeChat group information, public account push information) before proceeding to the next operation. The server will only acknowledge this message. If the client has received it, it won't confirm that both clients have received it (I think).