WeChat public platform token verification failed

Today re-access to the public platform this error, the code has not changed anything, a few days ago, the public today suddenly unable to provide services ... Has anyone encountered this error?

It is also possible to verify the message through the Debug tool. The code has not changed, I do not know whether the public platform and updated what ...

Reply content:

Today re-access to the public platform this error, the code has not changed anything, a few days ago, the public today suddenly unable to provide services ... Has anyone encountered this error?

It is also possible to verify the message through the Debug tool. The code has not changed, I do not know whether the public platform and updated what ...

The time to verify is to go valid ()

The debugging to the midnight, valid there go unexpectedly is get, and the message is post ... I remember it used to be post.

Just now I have encountered this problem, the first to say their own background:

Last night docking a robot, and this morning is ready to change back to the original interface on the SAE, and then reported the same as you wrong. After initializing a good class, the call is: $wechatObj->responseMsg(); . After seeing the first answer, I changed it back: $wechatObj->valid(); then I submitted it and finally passed it. In summary: when you change from another interface back to the original interface, you have to go through the valid method .

Detour, there's a packaged SDK.

How to set the request address?

I met a very wonderful mistake: Error_reporting not set to 0, resulting in the output of the time there is a notice error, so always token verification failed, token verification failed, token verification failed ...

