cn.jpush.im.android.api.model.UserInfo.getNoDisturb()崩溃

jmessage
标签: #<Tag:0x00007fb84636cfd0>

(Android资深粘贴员) #1

在接入客服后,发送一条消息应用崩溃以下是崩溃信息
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: java.lang.NullPointerException: Attempt to invoke virtual method ‘int cn.jpush.im.android.api.model.UserInfo.getNoDisturb()’ on a null object reference
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: at cn.jpush.im.android.common.a.b(ChatMsgManager.java)
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: at cn.jpush.im.android.common.a.b(ChatMsgManager.java)
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: at cn.jpush.im.android.common.a.a(ChatMsgManager.java)
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: at cn.jpush.im.android.common.a$1.run(ChatMsgManager.java)
05-29 17:41:30.012 1229-4493/com.sh.android.EGold.activity W/System.err: at java.lang.Thread.run(Thread.java:761)
05-29 17:41:30.012 1229-4493/[图片]com.sh.android.EGold.activity W/System.err: at [图片]cn.jpush.im.android.common.a$1.run(ChatMsgManager.java)
05-29 17:41:30.012 1229-4493/[图片]com.sh.android.EGold.activity W/System.err: at java.lang.Thread.run(Thread.java:761)

这个问题困扰我很久了,也无法进行修改和抛异常,希望可以帮我解答疑惑


#2

请说明如下信息:
1、SDK的版本号
2、提供更多的信息,从初始化开始的 log 信息
3、你调什么 API 的时候报了错


(Android资深粘贴员) #3

1 : 2.4.1

2 :

05-29 18:01:21.632 18596-18596/? I/art: Late-enabling -Xcheck:jni
05-29 18:01:21.667 18596-18603/? I/art: Debugger is no longer active
05-29 18:01:21.667 18596-18603/? I/art: Starting a blocking GC Instrumentation
05-29 18:01:21.700 18596-18596/? I/MultiDex: VM with version 2.1.0 has multidex support
05-29 18:01:21.700 18596-18596/? I/MultiDex: install
05-29 18:01:21.700 18596-18596/? I/MultiDex: VM has multidex support, MultiDex support library is disabled.
05-29 18:01:21.720 18596-18596/? W/Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
05-29 18:01:21.740 18596-18596/? D/JIGUANG-JCore: [JCoreGlobal] metadata: appKey - d605c142cdd46829b13cbc8c
05-29 18:01:21.741 18596-18596/? D/JIGUANG-JCore: [JCoreGlobal] metadata: channel - Android
05-29 18:01:21.742 18596-18596/? D/JIGUANG-JCore: [AndroidUtil] action:checkValidManifest
05-29 18:01:21.746 18596-18596/? D/JIGUANG-JCore: [JCoreServiceUtils] set Push/Alarm Receiver enabled
05-29 18:01:21.752 18596-18596/? D/JIGUANG-JCore: [JCoreGlobal] action:init - sdkVersion:1.1.8, buildId:163
05-29 18:01:21.768 18596-18596/? I/JIGUANG-JMessage: [JMessageClient] JMessage SDK init finished! version = 2.4.1 build id = 916
05-29 18:01:21.769 18596-18596/? D/JIGUANG-JPush: [JPushInterface] action:init - sdkVersion:3.1.0, buildId:391
05-29 18:01:21.769 18596-18596/? D/JIGUANG-JPush: [AndroidUtil] action:checkValidManifest
05-29 18:01:21.769 18596-18596/? W/JIGUANG-JPush: [AndroidUtil] AndroidManifest.xml missing required service: cn.jpush.android.service.DaemonService
05-29 18:01:21.771 18596-18596/? W/JIGUANG-JPush: [AndroidUtil] AndroidManifest.xml missing activity: cn.jpush.android.ui.PopWinActivity
05-29 18:01:21.771 18596-18596/? W/JIGUANG-JPush: [AndroidUtil] You will unable to use pop-window rich push type.
05-29 18:01:21.777 18596-18596/? I/JIGUANG-JPush: [PluginPlatformsInterface] whichPlatform - 0
05-29 18:01:21.777 18596-18596/? I/JIGUANG-JPush: [PluginPlatformsInterface] isIntegrateFCM -false
05-29 18:01:21.778 18596-18596/? E/JIGUANG: 100d85590914e455ad9
05-29 18:01:21.786 18596-18596/? D/JIGUANG-JAnalytics: [JAnalyticsInterface] JAnalyticsInterface init...version:1.1.2 ,buildId:126
05-29 18:01:21.789 18596-18596/? I/System: Daemon delayGCRequest, sDelayGCRequest=false, delay=true, sPendingGCRequest=false
05-29 18:01:21.867 18596-18649/? D/OpenGLRenderer: RenderMonitor init!
05-29 18:01:21.867 18596-18649/? D/OpenGLRenderer: RenderMonitor closed!
05-29 18:01:21.879 18596-18596/? I/IgnoreTouchEvent: ignoreTouchEvent onWindowAttached
                                                     
                                                     [ 05-29 18:01:21.884   711:  711 D/         ]
                                                     SurfaceMonitor closed!
05-29 18:01:21.899 18596-18649/? I/Adreno: QUALCOMM build                   : 122086c, I10f26366c1
                                           Build Date                       : 08/30/17
                                           OpenGL ES Shader Compiler Version: XE031.14.00.04
                                           Local Branch                     : 
                                           Remote Branch                    : 
                                           Remote Branch                    : 
                                           Reconstruct Branch               : 
05-29 18:01:21.900 18596-18649/? I/Adreno: PFP: 0x005ff087, ME: 0x005ff063
05-29 18:01:21.911 18596-18650/? D/NetworkSecurityConfig: No Network Security Config specified, using platform default
05-29 18:01:21.914 18596-18649/? I/OpenGLRenderer: Initialized EGL, version 1.4
05-29 18:01:21.914 18596-18649/? D/OpenGLRenderer: Swap behavior 1
05-29 18:01:21.914 18596-18650/? I/DpmTcmClient: RegisterTcmMonitor from: com.android.okhttp.TcmIdleTimerMonitor
05-29 18:01:21.991 18596-18650/? D/JIGUANG-JCore: [HttpHelper] status code:200
05-29 18:01:21.991 18596-18650/? D/JIGUANG-JCore: [ReportUtils] JANALYTICS,report success
05-29 18:01:23.290 18596-18596/com.sh.android.EGold.activity I/System: Daemon delayGCRequest, sDelayGCRequest=true, delay=false, sPendingGCRequest=false

3 :崩溃前我有调用JMessageClient.login 登录与 message.setOnSendCompleteCallback 发送
都成功后 突然崩溃


(Android资深粘贴员) #4

我自己认为有可能是切换用户后再去登录和发送 崩溃几率很大


#5

已反馈给研发分析。


(jinfengf) #6

提供一下完整的日志


(Android资深粘贴员) #7

极光错误日志.txt (41.8 KB)
全部的日志


(Android资深粘贴员) #8

这个问题是出在哪里呀


#9

该问题是频繁登录登出造成的。
该场景应该是只在你测试时会出现,对客户来说,应不会出现频繁的登陆登出,即对实际用户不会产生该崩溃。

研发将考虑一下是否可以从 SDK 层面做优化


(Android资深粘贴员) #10

这边需求是,聊天双方都不固定 客户或者客服每次对话都不一定会是同一个人 所以每次都会获取新的账号密码登录,我这边没有好的办法


(Android资深粘贴员) #11

其实也不是很频繁,就切换了一次 就崩溃了


(jinfengf) #12

SDK后续版本会对这个问题进行修复


(Android资深粘贴员) #13

现在有没有什么好的办法可以临时解决


(jinfengf) #14

上层也没有很好的办法控制,这个主要是由于切换用户那一刻,收到消息,消息处理过程中切换用户造成