What should I do if the following issue occurs when I use APls with JNI?
Exception in thread "main" java.lang.UnsatisfiedLinkError: *** Can't load IA 32-bit *** on a AMD 64-bit platform
This indicates a typical mismatch between JVM and the dynamic library. To fix it, use a 32-bit dynamic library to load a 32-bit JVM.
How can I generate a UserSig?
What is the validity period of UserSig?
As an important credential for Chat login authentication, UserSig has a default validity period of 180 days, which can only be modified through the native API. Other APIs and tools cannot modify the validity period. The validity period of UserSig can be set to a maximum of 10 years. You are advised to set the validity period to two months for your account security. For more information, see Generating UserSig. Why do I encounter error 70009 upon login?
UserSig verification fails, which may be caused by mixing keys or private keys of other SDKAppIDs when generating UserSig. Please use the key or private key under the corresponding SDKAppID to regenerate UserSig.
What should I do if the following issues occur when the Chat account is not imported?
Error 10019 is reported:
The UserID in the request does not exist. Check whether each Member_Account in MemberList is correct.
Error 10007 is reported:
You do not have the operation permissions. (For example, a common member in a public group attempts to remove a member from the group, but only the app administrator has the permission to do so.)
Error 20003 is reported:
The UserID of the sender or recipient is invalid or does not exist. Check whether the UserID has been imported into the Chat console.
Note:
You need to generate accounts and import them into Chat via an API call. The accounts can be used only after imported.