差别
这里会显示出您选择的修订版和当前版本之间的差别。
两侧同时换到之前的修订记录 前一修订版 后一修订版 | 前一修订版 后一修订版 两侧同时换到之后的修订记录 | ||
im:android:push:troubleshooting [2019/09/20 13:07] huanxinfudh |
im:android:push:troubleshooting [2019/11/21 02:56] huanxinfudh |
||
---|---|---|---|
行 35: | 行 35: | ||
2019-09-02 10:50:35.988 5446-5475/? D/ONE SDK: [2019/09/02 10:50:35:988]: [EMPushHelper] EMPushHelper register, prefer push type: HMSPUSH | 2019-09-02 10:50:35.988 5446-5475/? D/ONE SDK: [2019/09/02 10:50:35:988]: [EMPushHelper] EMPushHelper register, prefer push type: HMSPUSH | ||
- | //2、这是获取到了华为返回的推送token,这里的推送token可以在华为的推送后台去指定用户测试推送 | + | //2、获取到了华为返回的推送token,这里的推送token可以在华为的推送后台去指定用户测试推送 |
2019-09-02 10:50:38.298 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] onReceiveToken: HMSPUSH - 0869379034831543200000121400CN01 | 2019-09-02 10:50:38.298 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] onReceiveToken: HMSPUSH - 0869379034831543200000121400CN01 | ||
行 42: | 行 42: | ||
2019-09-02 10:50:38.298 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] Retry upload after 262s if failed. | 2019-09-02 10:50:38.298 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] Retry upload after 262s if failed. | ||
- | //3、这是去上传推送token,后面有对应的证书名称 | + | //3、去上传推送token,后面有对应的证书名称 |
- | 2019-09-02 10:50:38.299 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] uploadTokenInternal, token=0869379034831543200000121400CN01, url=https://a4.easemob.com:443/easemob-demo/chatdemoui/users/wx1994, notifier name=10492024 | + | 2019-09-02 10:50:38.299 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:298]: [EMPushHelper] uploadTokenInternal, token=0869379034831543200000121400CN01, url=https://a4.easemob.com:443/easemob-demo/chatdemoui/users/omg4, notifier name=10492024 |
- | //4、这是推送token上传成功 | + | //4、推送token上传成功 |
2019-09-02 10:50:38.451 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:450]: [EMPushHelper] uploadTokenInternal success. | 2019-09-02 10:50:38.451 5446-5475/? D/ONE SDK: [2019/09/02 10:50:38:450]: [EMPushHelper] uploadTokenInternal success. | ||
</code> | </code> | ||
行 146: | 行 146: | ||
2019-09-03 15:52:57.275 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:275]: [EMPushHelper] EMPushHelper register, prefer push type: MIPUSH | 2019-09-03 15:52:57.275 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:275]: [EMPushHelper] EMPushHelper register, prefer push type: MIPUSH | ||
- | //2、这是获取到了小米返回的推送token,这里的推送token就是小米推送的regid | + | //2、获取到了小米返回的推送token,这里的推送token就是小米推送的regid |
2019-09-03 15:52:57.725 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:725]: [EMPushHelper] onReceiveToken: MIPUSH - Tn0uw0uGRoadNgW6TElcKCGiEwrMCo39nWomRxQU0+K+WlqvFmaHSn45vr9fLG3k | 2019-09-03 15:52:57.725 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:725]: [EMPushHelper] onReceiveToken: MIPUSH - Tn0uw0uGRoadNgW6TElcKCGiEwrMCo39nWomRxQU0+K+WlqvFmaHSn45vr9fLG3k | ||
行 153: | 行 153: | ||
2019-09-03 15:52:57.725 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:725]: [EMPushHelper] Retry upload after 287s if failed. | 2019-09-03 15:52:57.725 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:725]: [EMPushHelper] Retry upload after 287s if failed. | ||
- | //3、这是去上传推送token,后面有对应的证书名称 | + | //3、去上传推送token,后面有对应的证书名称 |
- | 2019-09-03 15:52:57.726 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:726]: [EMPushHelper] uploadTokenInternal, token=Tn0uw0uGRoadNgW6TElcKCGiEwrMCo39nWomRxQU0+K+WlqvFmaHSn45vr9fLG3k, url=https://a5-v2.easemob.com:443/easemob-demo/chatdemoui/users/wx1994, notifier name=2882303761517426801 | + | 2019-09-03 15:52:57.726 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:57:726]: [EMPushHelper] uploadTokenInternal, token=Tn0uw0uGRoadNgW6TElcKCGiEwrMCo39nWomRxQU0+K+WlqvFmaHSn45vr9fLG3k, url=https://a5-v2.easemob.com:443/easemob-demo/chatdemoui/users/omg4, notifier name=2882303761517426801 |
- | //4、这是推送token上传成功 | + | //4、推送token上传成功 |
2019-09-03 15:52:58.930 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:58:930]: [EMPushHelper] uploadTokenInternal success. | 2019-09-03 15:52:58.930 2984-3173/com.hyphenate.chatuidemo D/ONE SDK: [2019/09/03 15:52:58:930]: [EMPushHelper] uploadTokenInternal success. | ||
</code> | </code> | ||
+ | |||
+ | 上面的是上传推送token成功的日志,可以对比你本地logcat里的日志,看下是否完整。(''需在初始化环信SDK的时候设置EMClient.getInstance().setDebugMode(true)才会有详细的日志输出'') | ||
+ | |||
1、如果在这一步看到MIPUSH是false,那就是小米推送没有配置好,比如没有导入小米推送的jar,清单里的权限和配置没有加上,或者就是没有在初始化之前去设置上小米推送的appid和appkey。 | 1、如果在这一步看到MIPUSH是false,那就是小米推送没有配置好,比如没有导入小米推送的jar,清单里的权限和配置没有加上,或者就是没有在初始化之前去设置上小米推送的appid和appkey。 | ||
行 194: | 行 197: | ||
JSONObject extObject = new JSONObject(); | JSONObject extObject = new JSONObject(); | ||
try { | try { | ||
- | extObject.put("em_oppo_push_channel_id", "chanleid"); | + | extObject.put("em_oppo_push_channel_id", chanleid); |
} catch (JSONException e) { | } catch (JSONException e) { | ||
e.printStackTrace(); | e.printStackTrace(); | ||
行 204: | 行 207: | ||
集成完成之后运行app去登录,在logcat里检索EMPushHelper查看日志确定下是否集成成功 | 集成完成之后运行app去登录,在logcat里检索EMPushHelper查看日志确定下是否集成成功 | ||
<code> | <code> | ||
- | //1、SDK判断当前设备小米推送可用 | + | //1、SDK判断当前设备OPPO推送可用 |
2019-09-06 14:21:27.532 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:531]: [EMPushHelper] isSupportPush: FCM - false | 2019-09-06 14:21:27.532 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:531]: [EMPushHelper] isSupportPush: FCM - false | ||
2019-09-06 14:21:27.556 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:555]: [EMPushHelper] isSupportPush: MIPUSH - false | 2019-09-06 14:21:27.556 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:555]: [EMPushHelper] isSupportPush: MIPUSH - false | ||
行 212: | 行 215: | ||
2019-09-06 14:21:27.610 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:610]: [EMPushHelper] EMPushHelper register, prefer push type: OPPOPUSH | 2019-09-06 14:21:27.610 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:610]: [EMPushHelper] EMPushHelper register, prefer push type: OPPOPUSH | ||
- | //2、这是获取到了OPPO返回的推送token | + | //2、获取到了OPPO返回的推送token |
2019-09-06 14:21:27.805 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:805]: [EMPushHelper] onReceiveToken: OPPOPUSH - CN_724a57d2233d2363fbdeff46af095155 | 2019-09-06 14:21:27.805 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:805]: [EMPushHelper] onReceiveToken: OPPOPUSH - CN_724a57d2233d2363fbdeff46af095155 | ||
行 219: | 行 222: | ||
2019-09-06 14:21:27.806 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:806]: [EMPushHelper] Retry upload after 469s if failed. | 2019-09-06 14:21:27.806 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:806]: [EMPushHelper] Retry upload after 469s if failed. | ||
- | //3、这是去上传推送token,后面有对应的证书名称 | + | //3、去上传推送token,后面有对应的证书名称 |
2019-09-06 14:21:27.807 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:807]: [EMPushHelper] uploadTokenInternal, token=CN_724a57d2233d2363fbdeff46af095155, url=https://a1.easemob.com:443/easemob-demo/chatdemoui/users/omg4, notifier name=65872dc4c26a446a8f29014f758c8272 | 2019-09-06 14:21:27.807 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:807]: [EMPushHelper] uploadTokenInternal, token=CN_724a57d2233d2363fbdeff46af095155, url=https://a1.easemob.com:443/easemob-demo/chatdemoui/users/omg4, notifier name=65872dc4c26a446a8f29014f758c8272 | ||
- | //4、这是推送token上传成功 | + | //4、推送token上传成功 |
2019-09-06 14:21:27.934 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:933]: [EMPushHelper] uploadTokenInternal success. | 2019-09-06 14:21:27.934 7852-7912/com.hyphenate.chatuidemo.push D/ONE SDK: [2019/09/06 14:21:27:933]: [EMPushHelper] uploadTokenInternal success. | ||
</code> | </code> | ||
+ | |||
+ | 上面的是上传推送token成功的日志,可以对比你本地logcat里的日志,看下是否完整。(''需在初始化环信SDK的时候设置EMClient.getInstance().setDebugMode(true)才会有详细的日志输出'') | ||
+ | |||
1、如果在这一步看到OPPOPUSH是false,那就是OPPO推送没有配置好,比如没有导入OPPO推送的jar,清单里的配置没有加上,或者就是没有在初始化之前去设置上OPPO推送的AppKey和AppSecret。 | 1、如果在这一步看到OPPOPUSH是false,那就是OPPO推送没有配置好,比如没有导入OPPO推送的jar,清单里的配置没有加上,或者就是没有在初始化之前去设置上OPPO推送的AppKey和AppSecret。 | ||
行 239: | 行 245: | ||
如果以上两步都没有去设置,需要提供消息内容、消息时间和接收方id反馈给环信来查 | 如果以上两步都没有去设置,需要提供消息内容、消息时间和接收方id反馈给环信来查 | ||
+ | ===== VIVO推送 ===== | ||
+ | |||
+ | 集成VIVO推送具体文件参考[[http://docs-im.easemob.com/im/android/push/thirdpartypush#vivo_%E6%8E%A8%E9%80%81%E9%9B%86%E6%88%90|VIVO推送集成]] | ||
+ | |||
+ | **集成OPPO推送时需要注意以下几点:** | ||
+ | |||
+ | 1、测试的VIVO机型是否是支持VIVO推送的,详情可见[[https://dev.vivo.com.cn/documentCenter/doc/156 | VIVO官网文档_支持机型和系统]] | ||
+ | |||
+ | 2、需要在手机通知管理里打开该应用的允许通知权限 | ||
+ | |||
+ | 集成完成之后运行app去登录,在logcat里检索EMPushHelper查看日志确定下是否集成成功 | ||
+ | |||
+ | <code> | ||
+ | //1、SDK判断当前设备VIVO推送可用 | ||
+ | 2019-10-14 14:57:33.231 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:231]: [EMPushHelper] isSupportPush: FCM - false | ||
+ | 2019-10-14 14:57:33.245 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:245]: [EMPushHelper] isSupportPush: MIPUSH - false | ||
+ | 2019-10-14 14:57:33.258 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:258]: [EMPushHelper] isSupportPush: HMSPUSH - false | ||
+ | 2019-10-14 14:57:33.272 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:272]: [EMPushHelper] isSupportPush: MEIZUPUSH - false | ||
+ | 2019-10-14 14:57:33.288 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:288]: [EMPushHelper] isSupportPush: OPPOPUSH - false | ||
+ | 2019-10-14 14:57:33.302 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:302]: [EMPushHelper] isSupportPush: VIVOPUSH - true | ||
+ | 2019-10-14 14:57:33.303 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:303]: [EMPushHelper] EMPushHelper register, prefer push type: VIVOPUSH | ||
+ | |||
+ | //2、获取到的VIVO返回的推送token | ||
+ | 2019-10-14 14:57:33.623 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:623]: [EMPushHelper] onReceiveToken: VIVOPUSH - 15665456497861102581637 | ||
+ | 2019-10-14 14:57:33.623 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:623]: [EMPushHelper] Retry upload after 4s if failed. | ||
+ | 2019-10-14 14:57:33.624 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:623]: [EMPushHelper] Retry upload after 9s if failed. | ||
+ | 2019-10-14 14:57:33.624 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:624]: [EMPushHelper] Retry upload after 301s if failed. | ||
+ | |||
+ | //3、去上传推送token,后面有对应的证书名称 | ||
+ | 2019-10-14 14:57:33.624 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:624]: [EMPushHelper] uploadTokenInternal, token=15665456497861102581637, url=https://a4.easemob.com:443/easemob-demo/chatdemoui/users/omg4, notifier name=11025#9b74dbfc-55c4-4441-9d0a-561ff21addc7 | ||
+ | |||
+ | //4、推送token上传成功 | ||
+ | 2019-10-14 14:57:33.760 24337-24437/com.hyphenate.chatuidemo D/ONE SDK: [2019/10/14 14:57:33:759]: [EMPushHelper] uploadTokenInternal success. | ||
+ | </code> | ||
+ | |||
+ | 上面的是上传推送token成功的日志,可以对比你本地logcat里的日志,看下是否完整。(''需在初始化环信SDK的时候设置EMClient.getInstance().setDebugMode(true)才会有详细的日志输出'') | ||
+ | |||
+ | 1、如果在这一步看到VIVOPUSH是false,那就是VIVO推送没有配置好,比如没有导入VIVO推送的jar,清单里没有去配置VIVO的appid和appkey | ||
+ | |||
+ | 2、如果没有看到VIVO返回的推送token的日志,那应该会有输出onErrorResponse:后面会有VIVO那边返回的错误码,需根据错误码去排查下 | ||
+ | |||
+ | 只要保证这两步是正常的,后面上传推送token的一般不会有问题,如果发现上传失败的情况,请反馈环信。然后在OPPO后台去使用推送token(在第二步中获取)给设备推送消息,收到之后就可以杀掉进程去测试离线推送了。 | ||
+ | |||
+ | 如果出现没有收到离线推送,需检查以下两步: | ||
+ | |||
+ | 1、是否有调用EMClient.getInstance().pushManager().disableOfflinePush去设置离线推送免打扰时间 | ||
+ | |||
+ | 2、如果是群组消息是否有调用EMClient.getInstance().pushManager().updatePushServiceForGroup去屏蔽群组离线推送 | ||
+ | |||
+ | 如果以上两步都没有去设置,需要提供消息内容、消息时间和接收方id反馈给环信来查 | ||