设置别名和 tags 总返回6002(每设置失败 8s 后再发请求)

error
标签: #<Tag:0x00007fb831ff6bd0>

#1
2017-02-07 10:10:50.092951 zhiligou copy[353:32489]  | JIGUANG | I - [JIGUANGService] 
--------------------------- JPush Log ----------------------------
--------------------JPush SDK Version:3.0.0--build:13----------
--------------------JCore Lib Version:1.0.0------------
-----------------AppKey:6269cbfd06561bacf148cafe----------------
----------------------------------------------------------------
2017-02-07 10:10:50.095172 zhiligou copy[353:32522]  | JIGUANG | I - [JIGUANGClientController] Action - jpush setup
2017-02-07 10:10:50.128702 zhiligou copy[353:32522]  | JIGUANG | I - [JIGUANGClientController] Action - setup
2017-02-07 10:10:50.424765 zhiligou copy[353:32513]  | JIGUANG | I - [JIGUANGBadgeNumberReport] set badge:0 succeed
2017-02-07 10:10:50.679683 zhiligou copy[353:32489]  | JIGUANG | I - [JIGUANGSessionController] connecting with coreAddr 139.198.190.13,port 7007
2017-02-07 10:10:50.906744 zhiligou copy[353:32525]  | JIGUANG | E - [JIGUANGTcpSocket] tcp read error occured: errocode 54
2017-02-07 10:10:52.960176 zhiligou copy[353:32513]  | JIGUANG | I - [JIGUANGSessionController] connecting with coreAddr 139.198.190.13,port 7007
2017-02-07 10:10:53.050153 zhiligou copy[353:32507]  | JIGUANG | I - [JIGUANGLogin] 
----- login result -----
uid:8422473294 
registrationID:101d8559094aa199959
2017-02-07 10:10:53.092976 zhiligou copy[353:32522]  | JIGUANG | I - [JIGUANGLogin] 
----- login result -----
uid:8422473294 
registrationID:101d8559094aa199959
2017-02-07 10:11:12.432997 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:11:41.249358 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:12:09.764829 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:12:36.755186 zhiligou copy[353:32771]  | JIGUANG | W - [JIGUANGNetworkController] 网络发生变化,重启session
2017-02-07 10:12:37.253783 zhiligou copy[353:32813]  | JIGUANG | I - [JIGUANGSessionController] connecting with coreAddr 139.198.190.34,port 7007
2017-02-07 10:12:37.676055 zhiligou copy[353:32813]  | JIGUANG | I - [JIGUANGLogin] 
----- login result -----
uid:8422473294 
registrationID:101d8559094aa199959
2017-02-07 10:12:38.591264 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:13:02.569428 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:13:07.406497 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:13:31.386729 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:13:35.599608 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:14:00.210352 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:14:04.420048 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:14:29.033106 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:14:32.572344 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:14:57.859101 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:15:01.394677 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:15:26.685470 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:15:30.220508 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:15:55.508825 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005
2017-02-07 10:15:59.045378 zhiligou copy[353:32395] iResCode:6002 iTags:{(
    User
)} iAlias:D5000000005

#2

目前的策略依旧是

设置tagalias的接口调用频率是5s以上,低于5s就会报6002超时
极光后台在短时间内不允许对同个设备重复设置别名和标签
2小时内,不支持对同个regid设置相同tag、alias值;
5s内也不支持对同个regid设置不同tag、alias值

如果是设置相同的,会直接返回成功,如果超频(5s内)会直接丢弃,客户端就是收不到响应

需要你自己加逻辑处理


#3

我是这样做的,如果设置失败,8s 后再调用这个接口的


#4

请问我要怎么处理这个问题?


#6

稍等一下,可能是我们这边的问题,正在确认排查


#7

好的,麻烦你们了,谢谢!


#8

现在OK了,你测试看看


(hoan) #9

大拿 咨询下 我这边 有的时候 tag值是可以注册成功的 。有的时候退出再登录进来 就报错6002.延时60s还是失败 就是没有注册成功 。 是否有方法保证注册一定成功?


#10

正常使用情况下报 6002 超时,只能重试。可以不用延迟 60 秒这么久


(hoan) #11

大拿 咨询下 我这边 有的时候 tag值是可以注册成功的 。有的时候退出再登录进来 就报错6002.延时 15s 还是失败 就是没有注册成功,只能重试 重试一直失败该肿么办 ? 是否有方法保证注册一定成功?


(hoan) #12

有的时候退出再登录进来 就报错6002.延时 15s 还是失败 就是没有注册成功,只能重试 但是重试一直失败该肿么办 ?


#13

如果你集成是成功的,但设置别名一直失败,很有可能是网络这时候有问题。
这种情况只能重试

或者客户端超时多次后告诉你们在服务端去调 API 设置
https://docs.jiguang.cn/jpush/server/push/rest_api_v3_device/


(hoan) #14

服务端调用? 服务端调用没用吧 我们要给客户端推东西 客户端没注册成功 我们该如何推?


#15

服务端调 device API 给你的客户端设置别名,如果他集成成功取到了 registrationID 只是别名设置不上,那你们可以在服务端给 registration ID设置别名然后给别名推消息,他就收的到!