装上我的iOS应用崩溃的新版本在App Store下载，只有当 [英] My new version of iOS app crash on loading only when loaded from the app store
问题描述
只为在我把它加载到应用程序商店我的应用程序崩溃。
一些背景，我已经测试与多个物理设备试飞的应用程序。该应用程序不会崩溃上的所有设备，先安装上设备工作正常（一种装置，从未有过的应用程序）。安装了该应用程序的原因之前，我测试的大多数设备崩溃的设备上。出现这种情况，即使我先删除了该设备的应用程序，然后从App Store安装。
一件事是，事故发生，从App Store安装时，设备上首次安装了旧版本，然后让我更新到新版本。在设备并没有崩溃，它直接加载新的版本（不首先安装旧版本）。
不知道如何解决，这将是非常美联社preciated，也想法如何在复制我的开发/测试环境的问题。
下面是设备之一的崩溃日志：
事件标识符：2F05957D-D4B0-49A0-9DEC-9F93AC008ED7
CrashReporter始终键：0dcfb6f747b264afdb9bc565deb821964c811b36
硬件型号：iPhone5,1
流程：SlimNavigator [10283]
路径：/var/mobile/Applications/C4110616-BE4C-4433-9FB9-C43F042D4CCA/SlimNavigator.app/SlimNavigator
标识符：SlimNavigator
版本：??? （???）
code类型：ARM（母语）
父进程：launchd的[1]日期/时间：2013年7月14日20：17：22.268 -0700
OS版本：6.1.4的iOS（10B350）
报告版本：104异常类型：EXC_BAD_ACCESS（SIGSEGV）
异常codeS：KERN_INVALID_ADDRESS在00000001
坠毁主题：0主题0名：调度队列：com.apple.main线程
螺纹0坠毁：
0 SlimNavigator 0x0010ad46 + NSHTTPCookieStorage（DeleteForURL）deleteCookiesForURL：]（NSHTTPCookieStorage + DeleteForURL.m：20）
1 dyld的0x2ff076c0 ImageLoaderMachO :: doInitialization（ImageLoader的:: LinkContext常量和放大器;）+ 16
2 dyld的0x2ff04a36 ImageLoader的:: recursiveInitialization（ImageLoader的:: LinkContext常量和放大器;，unsigned int类型，ImageLoader的:: InitializerTimingList＆安培;）+ 382
3 dyld的0x2ff04870 ImageLoader的:: runInitializers（ImageLoader的:: LinkContext常量和放大器;，ImageLoader的:: InitializerTimingList＆安培;）+ 36
4 dyld的0x2fefbd0e dyld的:: initializeMainExecutable（）+ 174
5 dyld的0x2fefe85e dyld的:: _主（macho_header const的*，无符号长，整型，字符常量**，字符常量**，字符常量**型，unsigned long *）+ 1802
6 dyld的0x2fefb32c dyldbootstrap ::开始（macho_header const的*，整型，字符常量**，长，macho_header const的*，无符号长*）+ 604
7 dyld的0x2fefb064 _dyld_start + 60螺纹0坠毁与ARM线程状态（32位）：
R0：00000001 R1：0x2fd8fd3c R2：00000000 R3：0x2fd8fd68
R4：0x000000a5 R5：00000000 R6：0x0010ad55 R7：0x2fd8eb18
R8：0x2ff1d674 R9：0x0000a100 R10：00000000 R11：00000001
IP：0x0000a100 SP：0x2fd8eae0 LR：0x2ff075b5 PC：0x0010ad46
CPSR：0x40000030二值图像：
0x71000 - 0x20bfff + SlimNavigator的ARMv7＆LT; 65ab2d7c06c932f6b3925448d72d95bf＆GT; /var/mobile/Applications/C4110616-BE4C-4433-9FB9-C43F042D4CCA/SlimNavigator.app/SlimNavigator
0x2fefa000 - 0x2ff1afff dyld的armv7s＆LT; 67efe80b9d863d6bb30fe51e6e17b070＆GT; / usr / lib目录/ dyld的
0x304d9000 - 0x305bffff AVFoundation armv7s＆LT; 56f22385ccb73e31863f1fa9e0b621dd＆GT; /System/Library/Frameworks/AVFoundation.framework/AVFoundation
感谢大家对你的答案。问题解决了，有两个变化，我添加1 -all_load标志链接程序可以装入其中，事故发生的问题库，2.拆下来坠毁库方法可能调用。我仍然不知道为什么它的设备上运行的发布版本时，这个问题不就表现自我，只能从App Store构建发生。
最相关的意见的基础上的答案，我这方面的经验，我可以给，是比较调试和发布建设置，并试图改变他们以匹配发布设置（优化级别是第一个尝试）。
My app crash only on after I loaded it to the app store.
Some background, I have tested the app with test flight on multiple physical devices. The app doesn't crash on all devices, first install on a device works fine ( a device that never had the app). Install on a device that had the app before cause the crash on most devices I tested with. That happens even if I first removed the app from the device, and then installed it from the app store.
One more thing is that on the devices the crash happened, when installing from the app store it first installed the old version and then allowed me to update to the new version. On the devices it didn't crash it loaded the new version directly (without installing first the old version).
Any idea how to resolve this would be highly appreciated, and also ideas how to replicate the issue in my development / test environment.
Below is the crash log from one of the devices:
Incident Identifier: 2F05957D-D4B0-49A0-9DEC-9F93AC008ED7
CrashReporter Key: 0dcfb6f747b264afdb9bc565deb821964c811b36
Hardware Model: iPhone5,1
Process: SlimNavigator [10283]
Path: /var/mobile/Applications/C4110616-BE4C-4433-9FB9-C43F042D4CCA/SlimNavigator.app/SlimNavigator
Identifier: SlimNavigator
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-07-14 20:17:22.268 -0700
OS Version: iOS 6.1.4 (10B350)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000001
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 SlimNavigator 0x0010ad46 +[NSHTTPCookieStorage(DeleteForURL) deleteCookiesForURL:] (NSHTTPCookieStorage+DeleteForURL.m:20)
1 dyld 0x2ff076c0 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 16
2 dyld 0x2ff04a36 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 382
3 dyld 0x2ff04870 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 36
4 dyld 0x2fefbd0e dyld::initializeMainExecutable() + 174
5 dyld 0x2fefe85e dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 1802
6 dyld 0x2fefb32c dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 604
7 dyld 0x2fefb064 _dyld_start + 60
Thread 0 crashed with ARM Thread State (32-bit):
r0: 0x00000001 r1: 0x2fd8fd3c r2: 0x00000000 r3: 0x2fd8fd68
r4: 0x000000a5 r5: 0x00000000 r6: 0x0010ad55 r7: 0x2fd8eb18
r8: 0x2ff1d674 r9: 0x0000a100 r10: 0x00000000 r11: 0x00000001
ip: 0x0000a100 sp: 0x2fd8eae0 lr: 0x2ff075b5 pc: 0x0010ad46
cpsr: 0x40000030
Binary Images:
0x71000 - 0x20bfff +SlimNavigator armv7 <65ab2d7c06c932f6b3925448d72d95bf> /var/mobile/Applications/C4110616-BE4C-4433-9FB9-C43F042D4CCA/SlimNavigator.app/SlimNavigator
0x2fefa000 - 0x2ff1afff dyld armv7s <67efe80b9d863d6bb30fe51e6e17b070> /usr/lib/dyld
0x304d9000 - 0x305bffff AVFoundation armv7s <56f22385ccb73e31863f1fa9e0b621dd> /System/Library/Frameworks/AVFoundation.framework/AVFoundation
Thank you everyone for your answers. Problem solved, with two changes I added 1. -all_load flag to linker to load the problematic library where the crash happened, 2. Remove the possible call to the library method that crashed. I'm still not sure why it the issue don't manifest it self when running a release build on a device and only happen with the build from the app store.
The most relevant advice I can give based on the answers and my experience with this, is compare your debug and release "build setting" and try to change them to match the release setting ("optimization level" is the first one to try).
这篇关于装上我的iOS应用崩溃的新版本在App Store下载，只有当的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
