iOS10.0.1下面Bugly导致崩溃的问题

前两天提交了一个版本,审核被拒了,说是审核的时候应用崩溃,就奇怪了,提交之前没少做测试啊。还好附件给出了崩溃的日志,看了下是iOS10.0.1版本下审的,这也有点奇怪,iOS10还没大量放开,就开始用它审核了。

不管了,先解决问题,日志如下:

Incident Identifier: B6A7C6FE-D926-4193-89F3-AAA69F38F384  
CrashReporter Key:   617fbd5d073bb8adaeb2167ca3c15df9260f289c  
Hardware Model:      xxx  
Process:             wesp [709]  
Path:                /private/var/containers/Bundle/Application/BCB2E566-E81B-45B8-B658-15F5F639EB5C/wesp.app/wesp  
Identifier:          com.wepie.wesp  
Version:             161 (3.7.3)  
Code Type:           ARM-64 (Native)  
Role:                Foreground  
Parent Process:      launchd [1]  
Coalition:           com.wepie.wesp [720]


Date/Time:           2016-09-13 15:02:38.5653 -0700  
Launch Time:         2016-09-13 15:02:33.2726 -0700  
OS Version:          iPhone OS 10.0.1 (14A403)  
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)  
Exception Codes: 0x0000000000000000, 0x0000000000000000  
Exception Note:  EXC_CORPSE_NOTIFY  
Triggered by Thread:  0

Application Specific Information:  
abort() called  
BUG IN CLIENT OF LIBDISPATCH: dispatch_barrier_sync called on queue already owned by current thread  
Abort Cause 6242089088

Filtered syslog:  
None found

Last Exception Backtrace:  
(0x192a9c1c0 0x1914d455c 0x192a9c108 0x1009cc95c 0x1005e6fc4 0x191b2b348 0x10060858c 0x10060858c 0x100608430 0x1005f80c8 0x1005f7998 0x1005f84b4 0x1005fdd0c 0x100608d10 0x191925200 0x1919251c0 0x191933444 0x1919289a8 0x19193538c 0x1919350ec 0x191b2d2c8 0x191b2cdb4)

这个应该是GCD引起的,iOS10以下又不会出现,只好升级了iOS10、Xcode7调试后发现时Bugly这个第三方库引起的,注释掉就好了,这也就尴尬了,本来是捕获崩溃日志的,自己却导致了崩溃,赶紧提交新版本并申请加速审核通道。大家又用这个库的也要注意了。