【友盟+】开发者社区

推送集成报错:-11: accs bindapp error!

发表于 2017-11-22 20:45:55 | |阅读模式

topgoal
topgoal 发表于 2017-11-22 20:45:55 | 显示全部楼层 |阅读模式
报错信息:
11-22 20:40:50.974 7513-7513/com.topgoal.smart E/awcn.GlobalAppRuntimeInfo:   CurrentProcess:com.topgoal.smart TargetProcess:com.topgoal.smart
11-22 20:40:51.024 7513-7612/com.topgoal.smart E/awcn.SessionCenter: |[seq:[default]] onNetworkStatusChanged. reCreateSession networkStatus:WIFI
11-22 20:40:51.074 7513-7513/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  init awcn success!
11-22 20:40:51.094 7513-7617/com.topgoal.smart E/awcn.SessionCenter: |[seq:umeng:5a14d9b5f43e482a95000036] [Get]connect exception errMsg:accs session connecting forbidden in background url:https://umengacs.m.taobao.com
11-22 20:40:51.094 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  reSend dataid:2 retryTimes:1
11-22 20:40:51.094 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  cancel customDataId:ctrl_bindapp
11-22 20:40:51.564 7513-7612/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] [connect] host:https://umengacs.m.taobao.com connect :106.11.61.105:443 sessionId:1511354451571 SpdyProtocol,:http2_0rtt_open proxyIp,: proxyPort,:0
11-22 20:40:51.604 7513-7612/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:CONNECTING
11-22 20:40:51.634 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:CONNECTED
11-22 20:40:51.634 7513-7631/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  1 auth URL:https://umengacs.m.taobao.com/accs/auth?1=WUmr467K7B0DAHq1f6tiagIJ&2=742d980f4254521333a8c5870e75385f21007a2c9922b6ed78adb4364bf17cdf&3=umeng:5a14d9b5f43e482a95000036&5=1&6=wifi&7=46001&8=1.1.2&9=1511354451089&10=1&11=23&12=com.topgoal.smart&13=1.0&14=android@umeng&15=vivo Y66&16=vivo&17=221&19=0
11-22 20:40:51.684 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] spdySessionConnectCB connect connectTime:39 sslTime::2
11-22 20:40:51.804 7513-7631/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  AUTH httpStatusCode:403 seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1
11-22 20:40:51.804 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:AUTH_FAIL
11-22 20:40:51.804 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] force close! session:Session@[umeng:5a14d9b5f43e482a95000036.AWCN1_1|http2_0rtt_open]
11-22 20:40:51.804 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:DISCONNECTING
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession:  spdyStreamCloseCallback error status code:-2002
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  AUTH onFinish statusCode:-2002 seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:AUTH_FAIL
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] force close! session:Session@[umeng:5a14d9b5f43e482a95000036.AWCN1_1|http2_0rtt_open]
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:DISCONNECTING
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] spdySessionCloseCallback  errorCode::-2002
11-22 20:40:51.824 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_1] notifyStatus status:DISCONNECTED
11-22 20:40:51.824 7513-7612/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] [connect] host:https://umengacs.m.taobao.com connect :106.11.61.105:443 sessionId:1511354451840 SpdyProtocol,:http2_0rtt_open proxyIp,: proxyPort,:0
11-22 20:40:51.824 7513-7612/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] notifyStatus status:CONNECTING
11-22 20:40:51.864 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] notifyStatus status:CONNECTED
11-22 20:40:51.864 7513-7631/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  1 auth URL:https://umengacs.m.taobao.com/accs/auth?1=WUmr467K7B0DAHq1f6tiagIJ&2=742d980f4254521333a8c5870e75385f21007a2c9922b6ed78adb4364bf17cdf&3=umeng:5a14d9b5f43e482a95000036&5=1&6=wifi&7=46001&8=1.1.2&9=1511354451089&10=1&11=23&12=com.topgoal.smart&13=1.0&14=android@umeng&15=vivo Y66&16=vivo&17=221&19=0
11-22 20:40:51.864 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] spdySessionConnectCB connect connectTime:39 sslTime::1
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  AUTH httpStatusCode:403 seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] notifyStatus status:AUTH_FAIL
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] force close! session:Session@[umeng:5a14d9b5f43e482a95000036.AWCN1_2|http2_0rtt_open]
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] notifyStatus status:DISCONNECTING
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/awcn.TnetSpdySession: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] spdySessionCloseCallback  errorCode::-2002
11-22 20:40:51.924 7513-7631/com.topgoal.smart E/awcn.Session: |[seq:umeng:5a14d9b5f43e482a95000036.AWCN1_2] notifyStatus status:DISCONNECTED
11-22 20:40:53.104 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  reSend dataid:2 retryTimes:2
11-22 20:40:53.104 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  cancel customDataId:ctrl_bindapp
11-22 20:40:55.114 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  reSend dataid:2 retryTimes:3
11-22 20:40:55.114 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  cancel customDataId:ctrl_bindapp
11-22 20:40:57.114 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  reSend dataid:2 retryTimes:4
11-22 20:40:57.114 7513-7617/com.topgoal.smart E/accs.InAppConn_umeng:5a14d9b5f43e482a95000036:  cancel customDataId:ctrl_bindapp


注册时的失败信息:
-11: accs bindapp error!

1、已检查填写的key和secret填写正确。
2、主工程和导出的module包含相同的so。
还是报以上错误。



上一篇:低版本Push SDK升级到最新3.3.5版本步骤有哪些?
下一篇:添加3.1.3版本后再4.4.4机器上崩溃

您需要登录后才可以发帖 登录 | 立即注册

本版积分规则

发表主题

精彩推荐

U-App即将升级,一站式运营你的“超级用户”
底部大福利,可优先体验内测账号哦~ 超级用户火了,因为互联网公司都感受到存量竞争的压力,App的运营核心
关于事件计算口径变更说明(2018.5.15)
影响范围:AppTrack产品全局数据1)计算基准的变更事件计算的周期基准变更:计算基于点击发生日期后续15天
友盟+大揭秘:阿里“亲橙里”的数据黑科技
4月28日,阿里首个智慧商业亲橙里开业。汇集盒马鲜生、天猫国际、天猫精灵、阿里小厨等众多业态,亲橙里通

关注我们

新浪微博
微信

欢迎关注友盟官方微博微信!

返回列表