推送问题,安卓和苹果

1011
error
收不到消息
标签: #<Tag:0x00007fb83faa8148> #<Tag:0x00007fb83faa7ec8> #<Tag:0x00007fb83faa7ce8>

(liudada ) #1

想问下,

  1. iOS端以前已经调试好了,能正常推送通知,包括跳转到相应的界面,但是我换了一个appkey ,代码完全没有变,改了appkley 当然也换了开发证书和生产证书和bundle id做开发环境测试,能收到到,做生产环境(打包)收不到,这样会不会是因为我证书问题?

2 iOS端,我用客户端之间发送通知收不到推送提醒,api 里面报红,显示1011 ,找不到目标对象,这部分是服务器原因,还是我的原因?

3.安卓端,我们一个app ,包含老师端和学生端,客户端之间能正常发送通知了,但是并不是所有手机能做测试,这是为什么?

4.安卓端,如果用后台服务器发送通知,就没有推送,报红,显示1011,(可能和第二个问题相同)


#2

1、该问题需要注意 app端配置的appkey有没有更换,可以给我提供信息来让我进行查询确认问题

2、1011错误的排查:

3、[quote=“liudada, post:1, topic:10942”]
并不是所有手机能做测试,这是为什么?
[/quote]

这个问题需要你详细描述一样,同样的可以提供信息给我查询


(liudada ) #4

| JPUSH | W - [JPUSHClientController] Not get deviceToken yet. Maybe: your certificate not configured APNs? or current network is not so good so APNs registration failed? or there is no APNs register code? Please refer to JPush docs.
显示不能得到,但是下面又还是得到token 了,
deviceToken2016-11-30 09:52:50.363 DG_SK[11876:1471376] Device Token: <b9425d3a 99e3d459 636a5c64 72efdc88 06116adb 02978469 3ecbef1b 935df18e>
就不知道到底是不是证书问题


#5

这个提示有一部分是因为网络原因,会重试,最终有成功即可。如果始终没有成功就需要排查问题:
Not get devicetoken 点我

从这段日志可以看出,你没有设置成功标签成功。


(liudada ) #6

奇怪,我开始都调试好了,包括能跳转到相应的界面了的,只是临时换了一个appkey ,并且都已经添加到代码和服务器里面了的,

这一部分显示我开发证书和生产证书没有问题的?


#7

不是很懂你的意思,即时判断就看当时的日志,然后去看代码。
这里显示你是失败的,在还没有注册成功的时候就调用了设置的API,自然无法成功,方法已经告知你。

我这句话已说明,如果你最终成功了,那么是这期间有网络问题导致出现这个提示,如果最终没有成功,就需要去排查问题,方法也已告知


(liudada ) #8

iOS 端已经调试好了,安卓端,我说的,有些手机可以有推送,有些手机,没有推送, 这是没有手机推送的日志

11-30 12:44:39.659 12819-12819/cc.vset.zixing D/JPush: [JPushInterface] action:resumePush
11-30 12:44:39.661 12819-12819/cc.vset.zixing D/JPush: [ServiceInterface] service is running already
11-30 12:44:39.687 12819-12819/cc.vset.zixing D/JPush: [JPushInterface] action:setAliasAndTags - alias:User_17037, tags:User_17037,Class_1321
11-30 12:44:39.695 12849-12849/? D/JPush: [PushService] onStartCommand - intent:Intent { act=cn.jpush.android.intent.ALIAS_TAGS cmp=cc.vset.zixing/cn.jpush.android.service.PushService (has extras) }, pkg:cc.vset.zixing, connection:-293289984
11-30 12:44:39.695 12849-12849/? D/JPush: [PushService] Action - handleServiceAction - action:cn.jpush.android.intent.ALIAS_TAGS
11-30 12:44:39.710 12849-12849/? D/JPush: [JPushRequestHelper] Action - sendJPushRequest - connection:-293289984, timeout:20000, threadId:1
11-30 12:44:39.753 12849-12881/? D/JPush: [NetworkingClient] Received bytes - len:31, connection:-293289984, pkg:cc.vset.zixing
11-30 12:44:39.753 12849-12881/? D/JPush: [NetworkingClient] Action - receivedCommand - cmd:19
11-30 12:44:39.753 12849-12881/? D/JPush: [NetworkingClient] Network listening...
11-30 12:44:39.897 12849-12881/? D/JPush: [NetworkingClient] Received bytes - len:100, connection:-293289984, pkg:cc.vset.zixing
11-30 12:44:39.900 12849-12881/? D/JPush: [NetworkingClient] Action - receivedCommand - cmd:3
11-30 12:44:39.926 12849-12881/? D/JPush: [NetworkingClient] Network listening...
11-30 12:44:40.899 14458-14458/cc.vset.zixing:push D/JPush: [JPushInterface] action:init - sdkVersion:2.2.0, buildId:335
11-30 12:44:40.930 14458-14458/cc.vset.zixing:push D/JPush: [JPushGlobal] metadata: appKey - 3f2a6d1e063b4725c97c489f
11-30 12:44:40.931 14458-14458/cc.vset.zixing:push D/JPush: [JPushGlobal] metadata: channel - developer-default
11-30 12:44:40.946 12849-12849/? D/JPush: [PushService] onStartCommand - intent:Intent { act=cn.jpush.android.intent.REPORT cmp=cc.vset.zixing/cn.jpush.android.service.PushService (has extras) }, pkg:cc.vset.zixing, connection:-293289984
11-30 12:44:40.946 12849-12849/? D/JPush: [PushService] Action - handleServiceAction - action:cn.jpush.android.intent.REPORT
11-30 12:44:40.948 12849-12849/? D/JPush: [PushService] onStartCommand - intent:Intent { act=cn.jpush.android.intent.INIT cmp=cc.vset.zixing/cn.jpush.android.service.PushService (has extras) }, pkg:cc.vset.zixing, connection:-293289984
11-30 12:44:40.948 12849-12849/? D/JPush: [PushService] Action - handleServiceAction - action:cn.jpush.android.intent.INIT
11-30 12:46:41.018 907-1062/? V/AlarmManager: sending alarm Alarm{77324a type 0 when 1480481196275 cc.vset.zixing whenElapsed 421194483 windowLength -1 maxWhen 421411983 repeatInterval 290000 action null component ComponentInfo{cc.vset.zixing/cn.jpush.android.service.AlarmReceiver}} success
11-30 12:46:41.022 12819-12819/cc.vset.zixing D/JPush: [AlarmReceiver] onReceive 
11-30 12:46:41.033 12849-12849/? D/JPush: [PushService] onStartCommand - intent:Intent { act=cn.jpush.android.intent.RTC cmp=cc.vset.zixing/cn.jpush.android.service.PushService (has extras) }, pkg:cc.vset.zixing, connection:-293289984
11-30 12:46:41.034 12849-12849/? D/JPush: [PushService] Action - handleServiceAction - action:cn.jpush.android.intent.RTC
11-30 12:46:41.041 12849-12849/? D/JPush: [PushService] Send heart beat
11-30 12:46:41.108 12849-12881/? D/JPush: [NetworkingClient] Received bytes - len:31, connection:-293289984, pkg:cc.vset.zixing
11-30 12:46:41.108 12849-12881/? D/JPush: [NetworkingClient] Action - receivedCommand - cmd:19
11-30 12:46:41.109 12849-12881/? D/JPush: [NetworkingClient] Network listening...
11-30 12:46:41.109 12849-12849/? D/JPush: [PushService] Action - onHeartbeatSucceed - connection:-293289984
11-30 12:46:43.728 12849-12849/? E/ANR_LOG: Blocked msg = { when=-2s620ms what=7303 target=cn.jpush.android.service.m } , cost  = 2619 ms

在api 里面 register id: 6370659590 显示推送成功


#9

根据你上一个提供的日志,我的判断是你设置tag的方式不对,导致失败,所以请你修正。

如果你已经调试好了就OK。

关于你现在提供的信息,[quote=“liudada, post:8, topic:10942”]
register id: 6370659590
[/quote]
这个应该是msgid,请提供该设备正确的registrationID。

Android这边,是需要考虑长连接的状态的。我这边看到的这条消息对应的两个Android目标,因为不在线,所以消息没有下发。

Android的排查步骤: