Exception in thread "main" java.lang.UnsatisfiedLinkError: com.tls.tls_sigcheck.tls_gen_signature_ex2(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)I at com.tls.tls_sigcheck.tls_gen_signature_ex2(Native Method) at Demo.main(Demo.java:31)
After ruling out the possibility of an incorrect dynamic library path, check whether the package path in the code is correct. API names are generated through the package path during JNI dynamic library compilation. Therefore, do not compile by modifying the package path in
tls_sigcheck.java, otherwise, the above issue will occur.
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 correct it, use a 32-bit dynamic library to load a 32-bit JVM.
For details, see Generating UserSig.
As an important credential for IM 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 50 years. You are advised to set the validity period to two months for your account security. For more information, see Generating UserSig.
Check whether the public and private keys match. Do not use the private key of the IM demo to generate UserSig.
You need to generate accounts and import them into IM via an API call. The accounts can be used only after imported.