我无法在任何iPhone和iPad上重现这个问题,所有构建在Debug,Release甚至与iTunes一起安装的ad-hoc构建的工作都很好.这是已有应用的更新.从以前版本添加的唯一内容是使用Azure通知中心的通知和版本检查.我正在使用最新版本的Xamarin iOS来创建应用程序
支持的体系结构是ARMv7 + ARM64
我试过了:
运行僵尸乐器
最小化启动负载
崩溃日志的一部分在这里,但我不能做任何事情
Incident Identifier: 533700FF-EE1C-4DFC-AFAD-60FE3600B66D
CrashReporter Key: 9cadde5ef1a33ebb1b6aeeaed6696a7ce8b4087d
Hardware Model: xxx
Process: TapNOrder [9390]
Path: /private/var/mobile/Containers/Bundle/Application/45780C57-DBB0-465C-872F-8A3BE6723261/TapNOrder.app/TapNOrder
Identifier: biz.innovative-ideas.tapnorder
Version: 0.1.7.2 (0.1.7)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2016-01-11 15:00:11.11 -0800
Launch Time: 2016-01-11 15:00:11.11 -0800
OS Version: iOS 9.2 (13C75)
Report Version: 105
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Triggered by Thread: 0
Filtered syslog:
None found
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 000000000000000000 0 + 0
1 TapNOrder 0x0000000100f8984c 0x1000a8000 + 15603788
2 TapNOrder 0x0000000100f88c40 0x1000a8000 + 15600704
3 TapNOrder 0x0000000100f88c78 0x1000a8000 + 15600760
4 TapNOrder 0x0000000100d7e570 0x1000a8000 + 13460848
5 libobjc.A.dylib 0x00000001827fab54 0x1827f4000 + 27476
6 libobjc.A.dylib 0x0000000182806080 0x1827f4000 + 73856
7 libobjc.A.dylib 0x00000001828060e0 0x1827f4000 + 73952
8 UIKit 0x000000018822fefc 0x187e6c000 + 3948284
...
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x00000001a0a82180 x3: 0x000000016fd55f08
x4: 0x000000013d88f680 x5: 0x0000000000000000 x6: 0x000000013d562090 x7: 0x0000000000000b20
x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000557 x11: 0x00000001a2f35929
x12: 0x00000001a2f35929 x13: 0x0000000000000001 x14: 0x000000008000001f x15: 0x0000000080000023
x16: 0x0000000182dfbaf4 x17: 0x00000001014082d8 x18: 0x0000000000000000 x19: 0x0000000101471870
x20: 0x000000013d562090 x21: 0x0000000182818fa6 x22: 0x0000000100d7e540 x23: 0x00000001a0a823e0
x24: 0x000000018280de80 x25: 0x000000019fb37616 x26: 0xf3002d81df52aec2 x27: 0x000000019feef000
x28: 0x000000019feef000 fp: 0x000000016fd55f20 lr: 0x0000000100f863b0
sp: 0x000000016fd55f10 pc: 0x0000000000000000 cpsr: 0xa0000000
完整的崩溃日志在这里:Apple Crash Log
有任何想法吗？
Crash Re Symbolication是查找确切崩溃问题的过程.
只需按照给定的步骤来解决崩溃问题.要从崩溃日志中获取符号化日志,您需要以下文件:
AppName.app - 应用程序文件(可执行文件)
AppName-dsym.dSYM - dSYM文件,由实际.app文件编译时由XCODE生成
AppName的崩溃,log.crash
仔细遵循所有步骤,然后检查崩溃日志,您将找到崩溃应用程序的确切位置.
现在按照以下给出的步骤:
将所有上述文件(AppName.app,AppName-dSYM.dSYM和AppName-Crash-log.crash)移动到具有方便名称的文件夹中,只要您轻松使用终端即可.只需在桌面上创建MyCrashReport文件夹并在其中添加所有三个文件.
转到以下适用于您的XCODE版本的路径:
Xcode 6
/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash
其他则是Xcode 6
内容/开发/平台/ iPhoneOS.platform /开发/库/ PrivateFrameworks/DTDeviceKitBase.framework /版本/ A /资源/ symbolicatecrash
要么
内容/开发/平台/ iPhoneOS.platform /开发/库/ PrivateFrameworks/DTDeviceKit.framework /版本/ A /资源/ symbolicatecrash
XCode 7.3
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
从此位置复制symbolicatecrash文件,并将其与以上三个文件粘贴在MyCrashReport文件夹中.
打开终端,将CD发送到MyCrashReport文件夹.
cd Desktop/MyCrashReport - 按Enter键
export DEVELOPER_DIR ="/ Applications/XCode.app/Contents/Developer" - 按Enter键
./symbolicatecrash -v AppName-Crash-log.crash AppName.dSYM - 按Enter键
完成!!!现在符号化日志在您的终端上,发现错误或崩溃.
请查看此链接以获取详细说明. https://medium.com/@Mrugraj/crash-re-symbolication-5c28d3a3a883#.4lvl4h625
京公网安备 11010802040832号 | 京ICP备19059560号-6 