在开始使用带有SecKeyGetBlockSize的IBM MobileFirst平台后，应用程序立即失败
在开始使用带有SecKeyGetBlockSize的IBM MobileFirst平台后，应用程序立即失败
提问于 2017-05-18 03:39:27
我们有很多用户，但只有几个人有这个问题。应用程序在启动后立即崩溃。Bitcode和ATS都被禁用。导致此问题的原因可能是什么？谢谢
Hardware Model: iPhone9,3
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Date/Time: 2017-05-16 18:05:01.2852 -0400
Launch Time: 2017-05-16 18:04:57.4399 -0400
OS Version: iPhone OS 10.3.1 (14E304)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread: 0
Thread 0 name:
Thread 0 Crashed:
SecKeyGetBlockSize + 0 (SecKey.c:696)
WLCertManager signData:privateKey:] + 276 (WLCertManager.m:525)
[WLDeviceAuthManager signDeviceAuth:entity:isPEnabled:] + 1168 (WLDeviceAuthManager.m:173)
[BaseProvisioningChallengeHandler onDeviceAuthDataReady:] + 172 (BaseProvisioningChallengeHandler.m:162)
[BaseDeviceAuthChallengeHandler getDeviceAuthDataAsync:] + 1308 (BaseDeviceAuthChallengeHandler.m:58)
[BaseProvisioningChallengeHandler handleChallenge:] + 1040 (BaseProvisioningChallengeHandler.m:138)
[WLRequest startHandleChallenges:httpRequest:]_block_invoke + 484 (WLRequest.m:606)
[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 136 (NSDictionary.m:680)
[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 180 (NSDictionary.m:692)
[WLRequest startHandleChallenges:httpRequest:] + 256 (WLRequest.m:598)
[WLRequest requestFailed:error:] + 604 (WLRequest.m:505)
[WLAFHTTPRequestOperationManagerWrapper requestFailed:error:] + 2020 (WLAFHTTPRequestOperationManagerWrapper.m:396)
[WLAFHTTPRequestOperationManagerWrapper start]_block_invoke229 + 112 (WLAFHTTPRequestOperationManagerWrapper.m:340)
[WLAFHTTPRequestOperation setCompletionBlockWithSuccess:failure:]_block_invoke42 + 112 (WLAFHTTPRequestOperation.m:141)
dispatch_call_block_and_release + 24 (init.c:963)
_dispatch_main_queue_callback_4CF + 444 (inline_internal.h:2417)
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1793)
__CFRunLoopRun + 1572 (CFRunLoop.c:3004)
CFRunLoopRunSpecific + 424 (CFRunLoop.c:3113)
GSEventRunModal + 100 (GSEvent.c:2245)
UIApplicationMain + 208 (UIApplication.m:4089)
main + 200 (main.swift:12)
libdyld.dylib 0x000000018eeb559c start + 4完整日志在此处https://drive.google.com/open?id=0B1GqBSG2XUgZYmhJVGFRakFtWUU
它看起来像是在我们做的时候发生的
private lazy var client: WLClient = WLClient.sharedInstance()
self.client.wlConnectWithDelegate(SomeDelegate)MFP版本= 7.1-2016/07/11
回答 3
Stack Overflow用户
发布于 2017-06-02 06:06:45
EXC_BAD_ACCESS是由空指针引用引起的。当wlConnectWithDelegate不止一次被调用时，我见过这种情况。
我会尝试这样使用Swift的dispatch_once_t单例：
var token: dispatch_once_t = 0
dispatch_once(&token) {
//Make sure you register all challenge handlers then connect
WLClient.sharedInstance().wlConnectWithDelegate(SomeDelegate)
}Stack Overflow用户
发布于 2017-06-02 15:33:28
异常看起来像是MobileFirst SDK中的密钥链访问错误。在7.1中，MobileFirst不支持后台模式。请确保您的应用程序未尝试从background.Also运行MobileFirst连接API确保在目标->功能中启用了"KeyChain共享“。
Stack Overflow用户
发布于 2017-11-10 17:00:28
该问题已在MobileFirst 7.1中修复并发布
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/44033460
复制相关文章
相似问题
腾讯云开发者
