应用程序拒绝了两次，但无法在iOS 9.2上重现该问题。我需要帮助确定它 [英] App rejected twice but cannot reproduce the issue on iOS 9.2. I need help identifying it
问题描述
我无法在任何iPhone和iPad上重现该问题，所有这些都基于Debug，Release，甚至使用iTunes工作安装的ad-hoc构建都很好。这是对现有应用的更新。从以前的版本添加的唯一的事情是使用Azure通知中心的通知和版本检查。我使用最新版本的Xamarin iOS创建应用程序
支持的架构是ARMv7 + ARM64
我尝试过：
- 运行僵尸工具
- 最小化启动负载
崩溃日志的一部分在这里，但我不能做任何事情。
code>事件标识符：533700FF-EE1C-4DFC-AFAD-60FE3600B66D
CrashReporter密钥：9cadde5ef1a33ebb1b6aeeaed6696a7ce8b4087d
硬件型号：xxx
过程：TapNOrder [9390]
路径： private / var / mobile / Containers / Bundle / Application / 45780C57-DBB0-465C-872F-8A3BE6723261 / TapNOrder.app / TapNOrder
标识符：biz.innovative-ideas.tapnorder
版本：0.1.7.2 0.1.7）
代码类型：ARM-64（Native）
父进程：launchd [1]
日期/时间：2016-01-11 15：00：11.11 -0800
发布时间：2016-01-11 15：00：11.11 -0800
操作系统版本：iOS 9.2（13C75）
报告版本：105
异常类型：EXC_BAD_ACCESS（SIGSEGV）
异常子类型：KERN_INVALID_ADDRESS在0x0000000000000000
线程触发：0
过滤的系统日志：
未找到
线程0名称：分派队列：com.apple.main线程
线程0崩溃：
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
...
线程0用ARM线程状态（64位）崩溃：
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：0x000000008000001f x15：0x0000000080000015
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
完整的崩溃日志这里：
按照所有步骤操作
现在按照以下给出的步骤：
-
将所有上述文件（AppName.app，AppName-dSYM.dSYM和AppName-Crash-log.crash）移动到一个具有方便名称的文件夹中， 。
-
转到下面适用于XCODE版本的路径：
Xcode 6
/Applications/Xcode.app/Contents/SharedFrameworks /DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash
其他Xcode 6
Platforms / iPhoneOS.platform / Developer / Library / PrivateFrameworks / DTDeviceKitBase.framework / Versions / A / Resources / symbolicatecrash
或
内容/ Developer / Platforms / iPhoneOS.platform / Developer / Library / PrivateFrameworks / DTDeviceKit.framework / Versions / A / Resources / symbolicatecrash
XCode 7.3
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
- 从此位置复制symbolicatecrash文件，并将其与上述三个文件粘贴到MyCrashReport文件夹中。
-
打开终端和CD到MyCrashReport文件夹。
-
导出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
I cannot reproduce the issue on any iPhone and iPad, all builds on Debug, Release and even the ad-hoc build installed with iTunes work just fine. This is an update of an already existing app. The only things added from the previous version are Notifications using Azure Notification Hubs and a version check. I am using the latest version of Xamarin iOS to create the app
The supported Architectures are ARMv7 + ARM64
I have tried:
- Running the zombies instrument
- Minimizing startup load
Part of the crash log is here but i cant make anything of it
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
The complete crash log is here: Apple Crash Log
Any ideas?
Crash Re Symbolication is process to find exact crash issue.
Just follow given steps to counter your crash issue. To get your symbolicated logs from Crash logs you will need following files:
- AppName.app — Application file (Executable)
- AppName-dsym.dSYM — dSYM file, generated by XCODE when actual .app file complied
- AppName-Crash-log.crash
Follow all the steps carefully and then check crash logs you will find exactly where it crashes the app.
Now follow below given steps :
Move all the above files (AppName.app, AppName-dSYM.dSYM and AppName-Crash-log.crash) into a Folder with a convenient name wherever you can go using Terminal easily. Simply create MyCrashReport folder on desktop and add all three files in it.
Go to the path from following whichever is applicable for your XCODE version :
Xcode 6
/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash
Other then Xcode 6
Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash
Or
Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks/DTDeviceKit.framework/Versions/A/Resources/symbolicatecrash
XCode 7.3
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
- Copy symbolicatecrash file from this location, and paste it with above three files in MyCrashReport folder.
Open Terminal, and CD to the MyCrashReport Folder.
cd Desktop/MyCrashReport — Press Enter
export DEVELOPER_DIR="/Applications/XCode.app/Contents/Developer" — Press Enter
./symbolicatecrash -v AppName-Crash-log.crash AppName.dSYM — Press Enter
Its done!!! Now Symbolicated logs are on your terminal and find out error or crash in it.
Check this link for detail description. https://medium.com/@Mrugraj/crash-re-symbolication-5c28d3a3a883#.4lvl4h625
这篇关于应用程序拒绝了两次，但无法在iOS 9.2上重现该问题。我需要帮助确定它的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
