05/15/2024 15:19:45

Solution

The business reception platform http://ptzh.sap.cm.com/ajax/ajax.html currently has two entries for querying gopenid. Both can satisfy the need. They are similar to the ability of querying gopenid through a QQ/WeChat account after an app goes online, as shown in the following diagram.

1. Gopenid query (query only) The game has opened the formal environment and there is data on the game side (the gopenid of the account has been generated in the backend: QQ/WeChat account has logged into the formal environment of the game or registered in the business reception platform through the "Gopenid registration" entrance). Only when the above conditions are met can the user query the gopenid of his QQ/WeChat account in the business reception platform through this entrance.
2. Gopenid registration Register gopenid through this entrance. The QQ/WeChat account will generate the gopenid of the account in the backend (no need for the game to go through the login process in the game). When the user needs to set the account whitelist during the joint debugging phase, he can set it by obtaining the corresponding gopenid of the QQ/WeChat account through this entrance.

Note: Theoretically, the game's gopenid is the same both in the test environment and the formal environment. However, it is not excluded that there is such a case that the account type generated for a game in the test environment is 32-bit, but the account type generated in the formal environment is 64-bit. At this case, if the account information of the test environment is retained, there will be inconsistency between the two environments (rare cases). If the account information of the test environment is cleared, the gopenid of the two environments will still be the same.