Android SDK FAQ

How appkey of the third-party platform corresponds to signature and package name?

When applying for appkey and secret on Sina Weibo and WeChat, you need to fill in the application’s signature and package name, as follows:
Fill in signature and package name on Sina Weibo: Why no callback after sharing to Wechat? - 图1
Fill in signature and package name on WeChat Why no callback after sharing to Wechat? - 图2
The appkey of Sina Weibo and WeChat correspond to the package name and signature. Therefore, the signature file configured in the program’s build.gradle must correspond to the package name of the third-party platform appkey and program configured in JGShareSDK.xml.

Why no callback after sharing to Wechat?

Check the package name and WeChat callback configuration configured in the AndroidMmanifest.xml file

  1. <!-- Optional 微信分享回调-->
  2. < activity
  3. android:name=".wxapi.WXEntryActivity"
  4. android:exported="true" />

The wxapi pointed to by the name field of WeChat callback must be in the package directory; if the path where the wxapi is located is not in the package directory, there is no callback.

Report an error when Weibo is sharing or authorizing: redirect_uri_mismatch

Report an error when sharing or authorizing
Why no callback after sharing to Wechat? - 图3
This error indicates that the callback address you configured in the JGShareSDK.xml file is inconsistent with the callback address of the Weibo open platform. Log in to the Sina Weibo open platform. Why no callback after sharing to Wechat? - 图4
Set the RedirectUrl of Weibo in JGShareSDK.xml to be the same as the authorized callback page address of Weibo open platform.