Technical FAQ

Why do I receive push when the app is open but not after force-quitting?

• If you only use the JPush proprietary channel, it relies on the app long connection being online. When offline, messages are cached on JPush servers and delivered when the app comes online again. See Cannot receive push when offline.
• If you also integrated vendor channels through JPush, verify that the vendor channel SDK integrated successfully, then use the JPush console troubleshooting tool to query the message lifecycle.
• If the notification reached the device but did not display, see Notification display issues.
• If the issue persists after the above steps, provide appkey, msgid, and regid to JPush online support, your dedicated technical support contact, or email support@jiguang.cn.

Why are messages not delivered via vendor channels?

• Verify that the vendor channel SDK integrated successfully.
• Check your server push strategy: channel selection is determined by the distribution field when pushing. See Push API protocol.
• Confirm whether you have JPush VIP service. Non-VIP customers have vendor channel delivery limits. See JPush platform limits.

How do I get Appkey, regid, and msgid?

See Required parameters for troubleshooting.

How do I get client logs?

If integration errors occur and client logs are needed, follow Client log collection for initial troubleshooting. If the issue remains, provide logs to technical support.

How do I push using tags and aliases?

See Tag and alias usage guide.

Why do tag and alias settings fail?

Tags and aliases have binding time limits and count limits. See Tag/alias setup issues.

How do I set a custom ringtone?

Only the JPush channel and some vendor channels support custom ringtones. See Custom ringtone setup.

How do I set notification images?

JPush supports large images, right-side icons, and status bar small icons. See Icon settings.

Vendor channel cannot navigate on click?

1. Confirm configuration per Android notification click navigation:

• Client: complete action, activity, and related configuration.
• Server: send intent in the required fixed format.

2. If push parameters contain special characters such as # or ;, encode vendor data. Set third_url_encode under notification.android.extras:

           "extras": {
 "third_url_encode": true //true means JPush performs encode
 }

 "extras": {
 "third_url_encode": false //false or omit: no JPush encode

        

Push returns 1011: "cannot find user by this audience or has been inactive for more than 255 days"

1011 means no matching push targets. See 1011 error troubleshooting.

iOS push environment mismatch (errcode: -16)

If the lifecycle tool shows "-16 iOS push environment mismatch", the registered token environment does not match the push environment parameter. See iOS push environment issues.