应用被拒绝:奇怪的 iPhone 崩溃日志 [英] App rejected: strange iPhone crash log
问题描述
由于启动时崩溃，Apple 两次拒绝了我的应用程序.我在不同的设备(iPhone 4、iPhone3GS、模拟器、iPad2)上对其进行了多次测试，它从未崩溃过.
Apple rejected my app two times due to a crash at launch. I have tested it many times on different devices (iPhone 4, iPhone3GS, Simulator, iPad2) and it never crashed.
这是符号化崩溃日志的一部分.
This is a part of the symbolicated crash log.
谢谢！
Incident Identifier: DD9A5C38-DFE5-4CB5-A15B-8C55967FFFD1
CrashReporter Key: bf318d2d968114ff69d458c2f8cbdc6b869e1ec7
Hardware Model: iPhone3,1
Process: iMetroRoma [2788]
Path: /var/mobile/Applications/8EC59E9D-D070-4CAD-892E-91BCE94AA58C/iMetroRoma.app/iMetroRoma
Identifier: iMetroRoma
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2011-10-24 13:23:22.895 -0700
OS Version: iPhone OS 5.0 (9A334)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Last Exception Backtrace:
0 CoreFoundation 0x30d828bf __exceptionPreprocess + 163
1 libobjc.A.dylib 0x37f271e5 objc_exception_throw + 33
2 CoreFoundation 0x30ccbb6b -[__NSArrayM objectAtIndex:] + 271
3 iMetroRoma 0x0000426f 0x1000 + 12911
4 CoreLocation 0x34fbc5df -[CLLocationManager onClientEventLocation:] + 1171
5 CoreLocation 0x34fbbf81 -[CLLocationManager onClientEvent:supportInfo:] + 201
6 CoreLocation 0x34fb662f __CLClientInvokeCallback_block_invoke_0 + 55
7 CoreFoundation 0x30d56b31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 13
8 CoreFoundation 0x30d5615f __CFRunLoopDoBlocks + 159
9 CoreFoundation 0x30d55381 __CFRunLoopRun + 1433
10 CoreFoundation 0x30cd84dd CFRunLoopRunSpecific + 301
11 CoreFoundation 0x30cd83a5 CFRunLoopRunInMode + 105
12 GraphicsServices 0x33906fed GSEventRunModal + 157
13 UIKit 0x32d4a743 UIApplicationMain + 1091
14 iMetroRoma 0x000024e3 0x1000 + 5347
15 iMetroRoma 0x0000249c 0x1000 + 5276
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3206732c __pthread_kill + 8
1 libsystem_c.dylib 0x3655df54 pthread_kill + 48
2 libsystem_c.dylib 0x36556fe4 abort + 88
3 libc++abi.dylib 0x31a1ff64 abort_message + 40
4 libc++abi.dylib 0x31a1d346 _ZL17default_terminatev + 18
5 libobjc.A.dylib 0x37f272dc _objc_terminate + 140
6 libc++abi.dylib 0x31a1d3be _ZL19safe_handler_callerPFvvE + 70
7 libc++abi.dylib 0x31a1d44a std::terminate() + 14
8 libc++abi.dylib 0x31a1e81e __cxa_rethrow + 82
9 libobjc.A.dylib 0x37f2722e objc_exception_rethrow + 6
10 CoreFoundation 0x30cd853e CFRunLoopRunSpecific + 398
11 CoreFoundation 0x30cd839e CFRunLoopRunInMode + 98
12 GraphicsServices 0x33906fe6 GSEventRunModal + 150
13 UIKit 0x32d4a73c UIApplicationMain + 1084
14 iMetroRoma 0x000024dc 0x1000 + 5340
15 iMetroRoma 0x00002494 0x1000 + 5268
...
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x00000000
r4: 0x00000006 r5: 0x3f54dce8 r6: 0x00000002 r7: 0x2fdffa6c
r8: 0x001a1c20 r9: 0x31a20a4a r10: 0x0000d224 r11: 0x0000cbfc
ip: 0x00000148 sp: 0x2fdffa60 lr: 0x3655df5b pc: 0x3206732c
cpsr: 0x00000010
...
推荐答案
好的，你提交到appstore的时候build and archive"了吗?
Okay, did you "build and archive" when submitting to appstore?
如果你没有，那就倒霉了.你现在能做的不多.即使您执行了构建和存档，但丢失了存档，您也很不走运.
If you did not, tough luck. There is not much you can do now. Even if you did Build and Archive, and lost the archive, you are out of luck.
如果你这样做了，存储分发构建的存档文件，非常好！
If you did however, store the archive file of distribution build, very good!
您是否尝试过在 XCode Organizer 中打开它(将文件拖放到管理器上，它应该尝试象征崩溃日志).如果没有，那就去做吧.
Have you tried opening this in XCode Organizer (drag and drop the file onto organizer, it should try to symbolicate the crashlog). If not, do it.
当你这样做时，有两种可能性:iMetroRoma 函数要么会被符号化(意味着你会看到哪一行导致它崩溃)，要么不会.
When you do it, there are two possibilities:
Either the iMetroRoma functions will get symbolicated (meaning you'll see which line is crashing it) or it wont.
X*:如果是这样，您就知道应用程序在哪里崩溃了.发布详细信息将帮助我们为您解决问题.
X*: If it does, you know where the application is crashing. Posting the details of that would help us solve the issue for you.
如果没有，则 XCode 中的自动符号化不起作用.请按照以下步骤操作(假设您从 XCode 4 完成了所有这些操作):
If it does not, then automatic symbolication in XCode is not working. Follow these steps (assuming you did all this from XCode 4):
- 从/Users/your_username/Library/Developer/Xcode/DerivedData 移除所有文件夹.
- 来自/Users/your_username/Library/Application支持/iPhone Simulator 删除所有文件夹.
- 清理你的垃圾.
然后尝试从 XCode Organizer 中删除该崩溃日志并再次将其拖放到那里.也许，它现在可能象征着它.如果确实执行了步骤 X*，如果没有，请继续阅读.
And then try deleting that crash log from XCode Organizer and drag/drop it again there. Possibly, it might symbolicate it now. If it does do step X*, If it does not, read on.
现在，您需要执行 按照步骤这个博客.(非常有用且有据可查的文章).
Now, you will need to do follow the steps on this blog. (Very useful and well documented article).
希望它会时不时地象征性地移动到第 X* 步.如果没有，我很抱歉无法提供帮助:)
Hopefully, it will symbolicate now and then move to step X*. If it does not, I'm sorry for not being able to help :)
这篇关于应用被拒绝:奇怪的 iPhone 崩溃日志的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
