Message garbled characters cannot be verified in the WeChat development mode and the Chinese characters of the returned messages

When the development mode cannot be verified or the Chinese characters of the returned message are garbled, the message is garbled.

At first, I had a long struggle with this issue. The example downloaded from the public platform was not in UTF-8 format, but it was verified.

At this time, the modification is added to the Chinese character, and the returned message will be garbled. If it is changed to UTF-8 encoding, it will be displayed as normal.

The verification fails.

I have been entangled in this issue, but it is not necessary. As long as the first verification is passed, the subsequent modification to UTF-8 encoding does not affect the interaction between public platforms and service numbers.

How to solve the garbled push information in the public platform development mode?

The reason for the character editing. You can use UTF8 in a unified manner.

The Information replied by the aspnet developer account is garbled in Chinese,

It should be the encoding problem. Try URLEncode encoding conversion.
Or ask if there are other official code conversions.