I do not know if you have encountered such a situation:
After OAuth obtains the user information, and correctly enters the H5 page, then click on the upper right corner ···
, click Refresh. The problem occurs: You cannot get the user again openid
.
How are you guys going to solve this? Do I know refresh_token
of one that is used to solve a similar situation?
Reply content:
I do not know if you have encountered such a situation:
After OAuth obtains the user information, and correctly enters the H5 page, then click on the upper right corner ···
, click Refresh. The problem occurs: You cannot get the user again openid
.
How are you guys going to solve this? Do I know refresh_token
of one that is used to solve a similar situation?
Obviously, you get openid
the way you need to start code-based, after the refresh without saving your openid
or last time access_token
, the last code is invalid, so must not get the user's OpenID,
Besides, if you openid
can't get it, you can use it refresh_token
to get it back.openid
You can use the cache to record OpenID or to return to the authorization page when no open is available.
Write a session.
Get the user information after you need to store AH brother!!!
I think you should take a closer look at the business process : https://github.com/thenbsp/wechat/wiki/o ...