android 初始化如何判断初始化是否成功


#127

是完整的,这是一份正常的日志


(12) #128

1 个帖子被分离到了新主题:10 条推送中有一条没有收到


(小股东) #129

你好 这是我们获取的极光 推送错误时 上传服务器的log,我是根据 长连接连接状态 判断的 您看一下log,是什么原因?

设备mac地址:e0:76:d0:d5:5b:73
--------- beginning of main
06-08 08:31:07.951 D/JIGUANG-JPush( 1489): [JPushInterface] action:init - sdkVersion:3.1.1, buildId:396
06-08 08:31:07.956 D/JIGUANG-JCore( 1489): [JCoreGlobal] metadata: appKey - 757bf908e1a2bcd0a064aacf
06-08 08:31:07.957 D/JIGUANG-JCore( 1489): [JCoreGlobal] metadata: channel - developer-default
--------- beginning of system
06-08 08:31:07.960 D/JIGUANG-JCore( 1489): [AndroidUtil] action:checkValidManifest
06-08 08:31:07.964 W/JIGUANG-JCore( 1489): [AndroidUtil] AndroidManifest.xml missing intent filter for DaemonService: cn.jpush.android.intent.DaemonService
06-08 08:31:07.966 D/JIGUANG-JCore( 1489): [JCoreServiceUtils] set Push/Alarm Receiver enabled
06-08 08:31:07.974 D/JIGUANG-JCore( 1489): [JCoreGlobal] action:init - sdkVersion:1.1.9, buildId:172
06-08 08:31:07.976 D/JIGUANG-JCore( 1489): [ServiceHelper] We found the appKey is changed or register appkey is empty. Will re-register.
06-08 08:31:07.984 D/JIGUANG-JPush( 1489): [AndroidUtil] action:checkValidManifest
06-08 08:31:07.987 E/JIGUANG-JPush( 1489): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-08 08:31:08.002 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.run.action cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.005 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.run.action cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.006 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - restartNetworkingClient, pid:1489
06-08 08:31:08.013 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.intent.RTC cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.015 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.cn.jpush.android.intent.check.notification.state cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.016 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.run.action cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.017 D/JIGUANG-JCore( 1489): [PushReceiver] onReceive - android.net.conn.CONNECTIVITY_CHANGE
06-08 08:31:08.019 D/JIGUANG-JCore( 1489): [ARunAction] pkg:com.aixuetang.future
06-08 08:31:08.019 D/JIGUANG-JCore( 1489): [ARunAction] Bundle[{action=cn.jpush.android.intent.REPORT, report.extra.info=, report=crash_log, sdktype=JCORE}]
06-08 08:31:08.020 I/JIGUANG-JCore( 1489): [NetworkingClient] Begin to run in ConnectingThread - id:219
06-08 08:31:08.024 D/JIGUANG-JCore( 1489): [ARunAction] pkg:com.aixuetang.future
06-08 08:31:08.025 D/JIGUANG-JCore( 1489): [ARunAction] Bundle[{action=cn.jpush.android.intent.REPORT, report.extra.info=, report=crash_log, sdktype=JCORE}]
06-08 08:31:08.026 D/JIGUANG-JPush( 1489): [AndroidUtil] action:checkValidManifest
06-08 08:31:08.029 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - restartNetworkingClient, pid:1489
06-08 08:31:08.031 E/JIGUANG-JPush( 1489): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-08 08:31:08.032 D/JIGUANG-JCore( 1489): [PushService] onStartCommand - intent:Intent { act=com.aixuetang.future.intent.CONNECTIVITY_CHANGE cmp=com.aixuetang.future/cn.jpush.android.service.PushService (has extras) }, pkg:com.aixuetang.future, connection:0
06-08 08:31:08.034 D/JIGUANG-JCore( 1489): [JiguangTcpManager] isRunning:true
06-08 08:31:08.094 D/JIGUANG-JCore( 1489): [ARunAction] pkg:com.aixuetang.future
06-08 08:31:08.095 D/JIGUANG-JCore( 1489): [ARunAction] Bundle[{action=cn.jpush.android.intent.REPORT, report.extra.info=, report=crash_log, sdktype=JCORE}]
06-08 08:31:08.098 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - restartNetworkingClient, pid:1489
06-08 08:31:08.100 D/JIGUANG-JCore( 1489): [JiguangTcpManager] isRunning:true
06-08 08:31:08.198 D/JIGUANG-JCore( 1489): [SisPolicy] To get sis - host:123.196.118.24, port:19000 ,type:hardcode
06-08 08:31:08.204 D/JIGUANG-JCore( 1489): [ConnectingHelper] SIS Receiving…
06-08 08:31:08.258 I/JIGUANG-JCore( 1489): [SisPolicy] Get sis info succeed with host: 123.196.118.24 type:hardcode
06-08 08:31:08.292 D/JIGUANG-JCore( 1489): [SisPolicy] Open connection with main - ip:123.196.118.5, port:7005
06-08 08:31:08.362 I/JIGUANG-JCore( 1489): [SisPolicy] Succeed to open connection - ip:123.196.118.5, port:7005
06-08 08:31:09.100 I/JIGUANG-JCore( 1489): [ConnectingHelper] Register succeed - juid:14038100815, registrationId:1104a897928fff3804e, deviceId:null
06-08 08:31:09.169 I/JIGUANG-JPush( 1489): [PluginPlatformsInterface] whichPlatform - 0
06-08 08:31:09.169 I/JIGUANG-JPush( 1489): [PluginPlatformsInterface] isIntegrateFCM -false
06-08 08:31:09.171 I/JIGUANG-JCore( 1489): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-08 08:31:09.243 W/JIGUANG-JCore( 1489): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-08 08:31:09.326 D/JIGUANG-JCore( 1489): [JiguangTcpManager] onLoginFailed - connection:219, respCode:0
06-08 08:31:10.186 I/JIGUANG-JCore( 1489): [ConnectingHelper] Register succeed - juid:14038100815, registrationId:1104a897928fff3804e, deviceId:null
06-08 08:31:10.240 I/JIGUANG-JCore( 1489): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-08 08:31:10.321 W/JIGUANG-JCore( 1489): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-08 08:31:10.366 D/JIGUANG-JCore( 1489): [JiguangTcpManager] onLoginFailed - connection:219, respCode:0
06-08 08:31:10.447 D/JIGUANG-JCore( 1489): [NetworkingClient] login error,retry login too many times
06-08 08:31:10.447 D/JIGUANG-JCore( 1489): [NetworkingClient] Action - closeConnection - connection:219
06-08 08:31:10.448 D/JIGUANG-JCore( 1489): [NetworkingClient] prepare Push Channel failed , returned
06-08 08:31:10.448 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - onDisconnected - connection:0
06-08 08:31:10.449 D/JIGUANG-JPush( 1489): [AndroidUtil] action:checkValidManifest
06-08 08:31:10.452 E/JIGUANG-JPush( 1489): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-08 08:31:10.452 D/JIGUANG-JCore( 1489): [NetworkingClient] Action - tryStop - connection:0
06-08 08:31:10.453 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - retryConnect - disconnectedTimes:0
06-08 08:31:11.101 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - restartNetworkingClient, pid:1489
06-08 08:31:11.102 D/JIGUANG-JCore( 1489): [JiguangTcpManager] isRunning:false
06-08 08:31:11.102 D/JIGUANG-JCore( 1489): [NetworkingClient] Action - tryStop - connection:0
06-08 08:31:11.103 I/JIGUANG-JCore( 1489): [NetworkingClient] Begin to run in ConnectingThread - id:226
06-08 08:31:11.156 D/JIGUANG-JCore( 1489): [SisPolicy] To get sis - host:123.196.118.24, port:19000 ,type:hardcode
06-08 08:31:11.160 D/JIGUANG-JCore( 1489): [ConnectingHelper] SIS Receiving…
06-08 08:31:11.254 I/JIGUANG-JCore( 1489): [SisPolicy] Get sis info succeed with host: 123.196.118.24 type:hardcode
06-08 08:31:11.272 D/JIGUANG-JCore( 1489): [SisPolicy] Open connection with main - ip:121.46.20.57, port:7004
06-08 08:31:11.332 I/JIGUANG-JCore( 1489): [SisPolicy] Succeed to open connection - ip:121.46.20.57, port:7004
06-08 08:31:12.044 I/JIGUANG-JCore( 1489): [ConnectingHelper] Register succeed - juid:14038100815, registrationId:1104a897928fff3804e, deviceId:null
06-08 08:31:12.085 I/JIGUANG-JCore( 1489): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-08 08:31:13.413 W/JIGUANG-JCore( 1489): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-08 08:31:13.465 D/JIGUANG-JCore( 1489): [JiguangTcpManager] onLoginFailed - connection:226, respCode:0
06-08 08:31:13.873 D/JIGUANG-JPush( 1337): [AndroidUtil] action:checkValidManifest
06-08 08:31:13.875 E/JIGUANG-JPush( 1337): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-08 08:31:13.876 W/JIGUANG-JPush( 1337): [TagAliasOperator] onTagaliasTimeout error:Attempt to invoke virtual method ‘java.lang.String java.lang.String.intern()’ on a null object reference
06-08 08:31:13.997 I/JIGUANG-JCore( 1489): [ConnectingHelper] Register succeed - juid:14038100815, registrationId:1104a897928fff3804e, deviceId:null
06-08 08:31:14.038 I/JIGUANG-JCore( 1489): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-08 08:31:14.144 W/JIGUANG-JCore( 1489): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-08 08:31:14.186 D/JIGUANG-JCore( 1489): [JiguangTcpManager] onLoginFailed - connection:226, respCode:0
06-08 08:31:14.285 D/JIGUANG-JCore( 1489): [NetworkingClient] login error,retry login too many times
06-08 08:31:14.285 D/JIGUANG-JCore( 1489): [NetworkingClient] Action - closeConnection - connection:226
06-08 08:31:14.285 D/JIGUANG-JCore( 1489): [NetworkingClient] prepare Push Channel failed , returned
06-08 08:31:14.285 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - onDisconnected - connection:0
06-08 08:31:14.286 D/JIGUANG-JPush( 1489): [AndroidUtil] action:checkValidManifest
06-08 08:31:14.287 E/JIGUANG-JPush( 1489): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-08 08:31:14.288 D/JIGUANG-JCore( 1489): [NetworkingClient] Action - tryStop - connection:0
06-08 08:31:14.288 D/JIGUANG-JCore( 1489): [JiguangTcpManager] Action - retryConnect - disconnectedTimes:1
06-08 08:31:14.290 D/JIGUANG-JCore( 1489): [JiguangTcpManager] onDisconnected and retry restart conn - delay:6000


(小股东) #130

我们这边有多份 错误日志

06-07 19:36:57.213 D/JIGUANG-JCore( 1524): [JiguangTcpManager] Action - restartNetworkingClient, pid:1524
06-07 19:36:57.213 D/JIGUANG-JCore( 1524): [JiguangTcpManager] isRunning:false
06-07 19:36:57.214 D/JIGUANG-JCore( 1524): [NetworkingClient] Action - tryStop - connection:0
06-07 19:36:57.214 I/JIGUANG-JCore( 1524): [NetworkingClient] Begin to run in ConnectingThread - id:261
--------- beginning of system
06-07 19:36:57.271 D/JIGUANG-JCore( 1524): [SisPolicy] To get sis - host:123.196.118.24, port:19000 ,type:hardcode
06-07 19:36:57.276 D/JIGUANG-JCore( 1524): [ConnectingHelper] SIS Receiving…
06-07 19:36:57.331 I/JIGUANG-JCore( 1524): [SisPolicy] Get sis info succeed with host: 123.196.118.24 type:hardcode
06-07 19:36:57.349 D/JIGUANG-JCore( 1524): [SisPolicy] Open connection with main - ip:139.198.188.45, port:7006
06-07 19:36:57.416 I/JIGUANG-JCore( 1524): [SisPolicy] Succeed to open connection - ip:139.198.188.45, port:7006
06-07 19:36:57.819 I/JIGUANG-JCore( 1524): [ConnectingHelper] Register succeed - juid:13434998535, registrationId:1104a8979289b862406, deviceId:null
06-07 19:36:57.865 I/JIGUANG-JCore( 1524): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-07 19:36:57.947 W/JIGUANG-JCore( 1524): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-07 19:36:57.989 D/JIGUANG-JCore( 1524): [JiguangTcpManager] onLoginFailed - connection:261, respCode:0
06-07 19:36:58.879 I/JIGUANG-JCore( 1524): [ConnectingHelper] Register succeed - juid:13434998535, registrationId:1104a8979289b862406, deviceId:null
06-07 19:36:58.939 I/JIGUANG-JCore( 1524): [ConnectingHelper] Login with - juid:0, appKey:757bf908e1a2bcd0a064aacf, sdkVersion:65801, pushVersion:196865, analyticsVersion:0 ,shareVersion:0, pluginPlatformType:0
06-07 19:36:59.024 W/JIGUANG-JCore( 1524): [ConnectingHelper] Login failed with server error - code:108 - Incorrect uid
06-07 19:36:59.070 D/JIGUANG-JCore( 1524): [JiguangTcpManager] onLoginFailed - connection:261, respCode:0
06-07 19:36:59.160 D/JIGUANG-JCore( 1524): [NetworkingClient] login error,retry login too many times
06-07 19:36:59.160 D/JIGUANG-JCore( 1524): [NetworkingClient] Action - closeConnection - connection:261
06-07 19:36:59.161 D/JIGUANG-JCore( 1524): [NetworkingClient] prepare Push Channel failed , returned
06-07 19:36:59.161 D/JIGUANG-JCore( 1524): [JiguangTcpManager] Action - onDisconnected - connection:0
06-07 19:36:59.161 D/JIGUANG-JPush( 1524): [AndroidUtil] action:checkValidManifest
06-07 19:36:59.163 E/JIGUANG-JPush( 1524): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-07 19:36:59.163 D/JIGUANG-JCore( 1524): [NetworkingClient] Action - tryStop - connection:0
06-07 19:36:59.163 D/JIGUANG-JCore( 1524): [JiguangTcpManager] Action - retryConnect - disconnectedTimes:9
06-07 19:37:02.275 D/JIGUANG-JPush( 2573): [AndroidUtil] action:checkValidManifest
06-07 19:37:02.277 E/JIGUANG-JPush( 2573): [AndroidUtil] AndroidManifest.xml missing required intent filter for PushActivity: cn.jpush.android.ui.PushActivity
06-07 19:37:02.277 W/JIGUANG-JPush( 2573): [TagAliasOperator] onTagaliasTimeout error:Attempt to invoke virtual method ‘java.lang.String java.lang.String.intern()’ on a null object reference


(12) #131

请不要重复提问,已经在另一帖里面回复过你。
https://community.jiguang.cn/t/topic/27106/14


(小股东) #132

你好 我们这边有一个问题,我们用的设备是定制的平板
我们将这个RegistrationID : 120c83f76028dd6b446 存在了我们服务器中

但我们发现这个RegistrationID 在不同学校的设备上 都出现了,这几个学校不是同一个地方的,学生用的也不是相同的设备,请问出现这样的问题是什么原因呢??


(12) #133

registrationID 可能存在重复的原因在本帖有说明


(12) #134

10 个帖子被分离到了新主题:别名报 6002


(小股东) #135

你好 -05 08:10:09.048 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:10:09.048 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12737, tags=null, alias=null, protoaction_type=3, sdktype=JPUSH}]
12-05 08:10:09.048 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:10:09.049 D/JIGUANG-JPush( 2288): [TagAliasHelper] tagalias:[TagaliasRequest] - appKey:757bf908e1a2bcd0a064aacf, action:{“platform”:“a”,“op”:“del”} - [Request] - [JHead] - len:0, version:1, command:29, rid:12737, sid:0, juid:0
12-05 08:10:09.049 D/JIGUANG-JPush( 2288): [JPushRequestHelper] Action - sendJPushRequest, timeout:20000, threadId:99
12-05 08:10:09.051 D/JIGUANG-JCore( 2288): [RequestCacheManager] Action - sendRequestInternal - connection:29995, timeout:20000,sdkType:JPUSH, threadId:96
12-05 08:10:10.062 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:10:10.062 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12739, tags=null, alias=211008254, protoaction_type=2, sdktype=JPUSH}]
12-05 08:10:10.062 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:10:10.068 E/JIGUANG-JPush( 2288): JPushMessageReceiverImp–onAliasOperatorResult6022
12-05 08:10:10.349 D/JIGUANG-JPush( 2288): [JPushDataAction] response:[TagaliasResponse] - action:{“code”:0} - JResponse{code=0}
12-05 08:10:10.355 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:10:10.355 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:10:41.253 D/JIGUANG-JCore( 2288): [JiguangTcpManager] Send heart beat
12-05 08:10:41.261 D/JIGUANG-JCore( 2288): [PushReceiver] onReceive - cn.jpush.android.intent.ACTION_REPORT_HISTORY
12-05 08:10:41.265 I/JIGUANG-JCore( 2288): [ReportHelper] periodTasks…
12-05 08:10:41.274 D/JIGUANG-JPush( 2288): [PushReceiverCore] onReceive - cn.jpush.android.intent.ACTION_REPORT_HISTORY
12-05 08:10:41.740 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:10:41.740 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:10:41.740 D/JIGUANG-JCore( 2288): [JiguangTcpManager] Action - onHeartbeatSucceed - connection:29995
12-05 08:13:17.014 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:13:17.014 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12743, tags=null, alias=null, protoaction_type=3, sdktype=JPUSH}]
12-05 08:13:17.014 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:13:17.015 D/JIGUANG-JPush( 2288): [TagAliasHelper] tagalias:[TagaliasRequest] - appKey:757bf908e1a2bcd0a064aacf, action:{“platform”:“a”,“op”:“del”} - [Request] - [JHead] - len:0, version:1, command:29, rid:12743, sid:0, juid:0
12-05 08:13:17.015 D/JIGUANG-JPush( 2288): [JPushRequestHelper] Action - sendJPushRequest, timeout:20000, threadId:99
12-05 08:13:17.017 D/JIGUANG-JCore( 2288): [RequestCacheManager] Action - sendRequestInternal - connection:29995, timeout:20000,sdkType:JPUSH, threadId:96
12-05 08:13:17.917 D/JIGUANG-JPush( 2288): [JPushDataAction] response:[TagaliasResponse] - action:{“code”:0} - JResponse{code=0}
12-05 08:13:17.919 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:13:17.919 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:13:18.035 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:13:18.035 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12745, tags=null, alias=211008283, protoaction_type=2, sdktype=JPUSH}]
12-05 08:13:18.035 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:13:18.036 D/JIGUANG-JPush( 2288): [TagAliasHelper] tagalias:[TagaliasRequest] - appKey:757bf908e1a2bcd0a064aacf, action:{“platform”:“a”,“op”:“set”,“alias”:“211008283”} - [Request] - [JHead] - len:0, version:1, command:29, rid:12745, sid:0, juid:0
12-05 08:13:18.037 D/JIGUANG-JPush( 2288): [JPushRequestHelper] Action - sendJPushRequest, timeout:20000, threadId:99
12-05 08:13:18.037 D/JIGUANG-JCore( 2288): [RequestCacheManager] Action - sendRequestInternal - connection:29995, timeout:20000,sdkType:JPUSH, threadId:96
12-05 08:13:18.924 D/JIGUANG-JPush( 2288): [JPushDataAction] response:[TagaliasResponse] - action:{“code”:0} - JResponse{code=0}
12-05 08:13:18.927 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:13:18.927 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:14:12.173 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:14:12.173 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12747, tags=null, alias=null, protoaction_type=3, sdktype=JPUSH}]
12-05 08:14:12.173 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:14:12.173 D/JIGUANG-JPush( 2288): [TagAliasHelper] tagalias:[TagaliasRequest] - appKey:757bf908e1a2bcd0a064aacf, action:{“platform”:“a”,“op”:“del”} - [Request] - [JHead] - len:0, version:1, command:29, rid:12747, sid:0, juid:0
12-05 08:14:12.173 D/JIGUANG-JPush( 2288): [JPushRequestHelper] Action - sendJPushRequest, timeout:20000, threadId:99
12-05 08:14:12.175 D/JIGUANG-JCore( 2288): [RequestCacheManager] Action - sendRequestInternal - connection:29995, timeout:20000,sdkType:JPUSH, threadId:96
12-05 08:14:13.182 D/JIGUANG-JPush( 2288): [JPushDataAction] Action - onActionRun
12-05 08:14:13.183 D/JIGUANG-JPush( 2288): [PushServiceCore] bundle:Bundle[{action=com.aixuetang.future.intent.ALIAS_TAGS, proto_type=2, seq_id=12749, tags=null, alias=211008254, protoaction_type=2, sdktype=JPUSH}]
12-05 08:14:13.183 D/JIGUANG-JPush( 2288): [PushServiceCore] Action - handleServiceAction - action:com.aixuetang.future.intent.ALIAS_TAGS
12-05 08:14:13.188 E/JIGUANG-JPush( 2288): JPushMessageReceiverImp–onAliasOperatorResult6022
12-05 08:14:13.380 D/JIGUANG-JPush( 2288): [JPushDataAction] response:[TagaliasResponse] - action:{“code”:0} - JResponse{code=0}
12-05 08:14:13.382 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:14:13.382 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:15:31.353 D/JIGUANG-JCore( 2288): [JiguangTcpManager] Send heart beat
12-05 08:15:31.357 D/JIGUANG-JCore( 2288): [PushReceiver] onReceive - cn.jpush.android.intent.ACTION_REPORT_HISTORY
12-05 08:15:31.357 D/JIGUANG-JPush( 2288): [PushReceiverCore] onReceive - cn.jpush.android.intent.ACTION_REPORT_HISTORY
12-05 08:15:31.361 I/JIGUANG-JCore( 2288): [ReportHelper] periodTasks…
12-05 08:15:31.514 D/JIGUANG-JCore( 2288): [NetworkingClient] Received bytes - len:36, connection:29995, pkg:com.aixuetang.future
12-05 08:15:31.515 D/JIGUANG-JCore( 2288): [NetworkingClient] Network listening…
12-05 08:15:31.516 D/JIGUANG-JCore( 2288): [JiguangTcpManager] Action - onHeartbeatSucceed - connection:29995

这是log日志

这是regisid :190e35f7e01e684d29f messageid:3741170079 286210744 894658741


(小股东) #136

请帮忙查一下 这个id 这几条信息都收到了吗 我们这边现象是没接收到信息


(12) #137

这个 registrationID 没有设置这些消息对应的别名值,不在这些消息的目标内!所以收不到,是正常情况


(小股东) #138

你的意思是app端没有调用 setalias()这个方法?


(12) #139

调没调 API 我不知道,但查到的结果是他没有设置别名。


(小股东) #140

你好 image
这个返回值是3 是什么意思呢


(小股东) #141

然后再帮我查看一下 “140fe1da9e8e9f460c8”,“1507bfd3f7ecb31353d”,“13065ffa4e5d13554e2”,“18071adc032283097f5”

这几个 regisid 的这几条信息 接收情况 messageid :893498007 2769549316 3475261013

还有这几个regisid 在今天8点左右的时候在线不在线


(小股东) #142

你好 还有这两个 regisid: 170976fa8aaef909145 170976fa8ad539e69c9

messageid:3741170079   3932176764

看一下这两个regisid 在8点半左右 信息的接收情况 谢谢了


(12) #143

返回值是什么意思,文档有
https://docs.jiguang.cn/jpush/server/push/rest_api_v3_report/#_7
3: registration_id 属于该应用,但不是该条 message 的推送目标;

在线,且都收到了消息

不属于这三条消息的目标,没有收到消息,所以当时在不在线看不到

在线收到了消息 893498007,其他的不在他们的目标内

能自己调 API 先查吗


(小股东) #144

你好 这里面有没有setalias()成功或者失败的信息? 我们这边服务器端 在app登录的时候都会去以别名做删除操作,,然后登录成功后,app端在setalias(),这样做有不妥的地方吗


(小股东) #145

你好 帮忙看一下这个 谢谢


(12) #146

删除

设置报 6022