Use QQ third-party login, mobile app and website application to the same QQ number, access to the OpenID is not the same
OpenID generation is based on the application of AppID and QQ number of some information encryption generated, for a appid and QQ number, OpenID is the only
The AppID used by the mobile app and the website app are not the same, so the OpenID you get will not be the same
So here's the problem.
The same QQ, through the mobile phone side of the third party login, and through the website login, because OpenID is not the same, will generate two users
Workaround:
send email to [email protected], content format:
Third-party login, the web-side returned OpenID inconsistent with OpenID returned by the mobile application two AppID merge mobile apps: APPID:111111111111APPKEY:ADSFASDFASDFASDFASDF website application: AppID : 222222222222APPKEY:ASDFASDFASDFSADFASDFASDF
After two or three days, you will receive a reply e-mail
The main idea is to ask you which AppID-based (if the mobile application-oriented, then the site application data before, it needs to provide QQ interconnection, it is more troublesome, I this direct to mobile application-oriented, Web application data will not be)
Then provide your company's business license and business license and website record Information inquiry
Send mail
This time is seconds back, five minutes not to reply to me,
Hello, the master-slave app has been successfully opened, please test to see. If the follow-up encounter problems, please timely email feedback, for you to verify the processing. If you encounter technical problems, you can contact the enterprise qq:800013811 for consultation, thank you! Warm tip: It is recommended to try not to modify the mobile AppID and website AppID and other information, avoid using error.
Also has been tossing for a long time, on-line also did not have the data to check,
Record it and hope to give some help to those who need it.
Use QQ third-party login, mobile app and website application to the same QQ number, access to the OpenID is not the same