无法复制Apple iOS app评论崩溃 [英] Cannot replicate Apple iOS app review crash
问题描述
我最近将我的iOS应用程序提交给Apple进行审核。它是用C＃编写的，使用Xamarin iOS，Monotouch和Monogame。我使用Xamarin IDE进行开发。一周之后，我得到拒绝，指出当评论者试图访问In-App-Purchase商店时应用程序在iPad上崩溃的原因，而在iPhone 5s上它没有崩溃，但表明它不能到达Apple服务器以检索商店项目。我的大部分商店检索代码均来自Xamarin的指南此处。
I recently submitted my iOS app to Apple for review. It was written in C# using Xamarin iOS, Monotouch and Monogame. I used the Xamarin IDE for development. A week later I get a rejection which specifies the reason being that the app crashes on iPad when the reviewer tries to access the In-App-Purchase store, while on the iPhone 5s it doesn't crash, but indicates that it couldn't reach the Apple servers to retrieve the store items. Much of my store retrieving code is from Xamarin's guide found here.
问题是我无法复制那些崩溃。商店和我一起开好了，我对它进行了广泛的测试。我在所有模拟器上进行了测试，并在调试和测试中使用了许多实际设备。发布配置（iPhone 4，iPhone 5，iPhone 5s，iPad第3代）。我没有在ad-hoc模式下测试，因为许多这些设备是从我的朋友那里借来的，我不想在iTunes中同步，因为这可能会消除设备数据。因此，我希望发布版本和ad-hoc在查找审核小组的错误方面是等效的。
The problem is that I could not replicate those crashes. The store opens just fine with me and I tested it extensively. I tested on all simulators, and many real devices in debug & release configurations (iPhone 4, iPhone 5, iPhone 5s, iPad 3rd generation). I didn't test in ad-hoc mode since many of these devices were borrowed from my friends and I didn't want to sync in iTunes since that could wipe out device data. So am hoping release build and ad-hoc are equivalent in terms of finding the review team's bug.
至于Apple给我的崩溃日志，他们没有帮助我，因为大多数行都没有使用我提交的相同档案在Xcode中正确符号化到Apple。日志中有很多'___lldb_unnamed_function'行。所有我能够分辨的是，在尝试检索商店时发生了崩溃。因此我陷入困境，不知道下一步该做什么。建议表示赞赏。
As for the crash logs given to me by Apple, they didn't help me since most lines don't get symbolicated properly in Xcode using the same archive that I submitted to Apple. There are a lot of '___lldb_unnamed_function' lines in the log. All i was able to tell was that the crash occurred when trying to retrieve the store. Therefore am stuck and not sure what to do next. Advice is appreciated.
以下是长崩溃日志的最后一部分。
Below is the last portion of a long crash log.
Incident Identifier: 24777CEA-21FF-434B-A658-BFB4BC89F7B2
CrashReporter Key: e981dd69858f1d35ba231cd2e288f3d33625919f
Hardware Model: xxx
Version: 1 (1)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2014-01-09 13:30:21.579 -0800
OS Version: iOS 7.0.4 (11B554a)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x387e41fc __pthread_kill + 8
1 libsystem_pthread.dylib 0x3884ba4f pthread_kill + 55
2 libsystem_c.dylib 0x38795029 abort + 73
3 MyGame 0x00d8036d mono_handle_native_sigsegv (mini-exceptions.c:2413)
4 MyBeGame 0x00d855b7 sigabrt_signal_handler (mini-posix.c:206)
5 libsystem_platform.dylib 0x38846721 _sigtramp + 41
6 libsystem_pthread.dylib 0x3884ba4f pthread_kill + 55
7 libsystem_c.dylib 0x38795029 abort + 73
8 MyBeGame 0x00e30744 monotouch_unhandled_exception_handler (monotouch-glue.m:1436)
9 MyBeGame 0x00d8072d mono_invoke_unhandled_exception_hook (mini-exceptions.c:2749)
10 MyBeGame 0x00d8d7ab mono_thread_abort_dummy (mini.c:2768)
11 MyBeGame 0x00d7ff35 mono_handle_exception_internal (mini-exceptions.c:1710)
12 MyBeGame 0x00d7f6b7 mono_handle_exception (mini-exceptions.c:2003)
13 MyBeGame 0x00d791b5 mono_arm_throw_exception (exceptions-arm.c:161)
14 MyBeGame 0x0023f7d4 ___lldb_unnamed_function12968$$MyBeGame + 64
15 MyBeGame 0x002da1d0 ___lldb_unnamed_function20307$$MyBeGame + 92
16 MyBeGame 0x00293960 ___lldb_unnamed_function17583$$MyBeGame + 196
17 MyBeGame 0x00212418 ___lldb_unnamed_function12101$$MyBeGame + 168
18 MyBeGame 0x0029205c ___lldb_unnamed_function17574$$MyBeGame + 92
19 MyBeGame 0x00295c58 ___lldb_unnamed_function17610$$MyBeGame + 32
20 MyBeGame 0x00083570 ___lldb_unnamed_function2892$$MyBeGame + 860
21 MyBeGame 0x000954f4 ___lldb_unnamed_function3194$$MyBeGame + 1516
22 MyBeGame 0x00093610 ___lldb_unnamed_function3176$$MyBeGame + 40
23 MyBeGame 0x0006246c MyBeGame.HintStoreController.HintStoreControl/StateRetrieving:<Activate>m__F + 624
24 MyBeGame 0x0045d39c ___lldb_unnamed_function33945$$MyBeGame + 48
25 MyBeGame 0x0020c10c ___lldb_unnamed_function11957$$MyBeGame + 196
26 MyBeGame 0x00d8ce4f mono_jit_runtime_invoke (mini.c:6504)
27 MyBeGame 0x00dd482b mono_runtime_invoke (object.c:2827)
28 MyBeGame 0x00d5117b native_to_managed_trampoline_MonoTouch_Foundation_InternalNSNotificationHandler_Post (registrar.m:28)
29 CoreFoundation 0x2da4fe6f __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 11
30 CoreFoundation 0x2d9c3aad _CFXNotificationPost + 1717
31 Foundation 0x2e3a9ec1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 69
推荐答案
您可以确定是否有两个版本通过比较，不同的配置（比如Release和Ad-Hoc）是相同的该项目的选择。特别要查看 Build / Compiler 和 Build / iOS Build 页面，并确保所有选项都相同。
You can determine if builds from two different configurations (say Release and Ad-Hoc) are identical by comparing the project's options. In particular look at the Build/Compiler and Build/iOS Build pages and make sure all the options are identical.
关于崩溃报告，我们不幸的是有一个 bug ，因此托管帧将无法正确符号化（这是所有lldb_unnamed_function条目的原因）。然而我能说的是应用程序崩溃，因为有一个未处理的托管异常。
Regarding the crash report we've unfortunately had a bug with the dSYM generation in Xamarin.iOS 7.0.4, so managed frames will not symbolicate correctly (this is the reason for all the lldb_unnamed_function entries). What I can say however is that the app is crashing because there is an unhandled managed exception.
如果你自己无法重现问题，我建议重建您的应用程序使用Xamarin.iOS 7.0.6（目前处于测试版频道），并重新提交给Apple。该应用程序可能仍会崩溃，但您应该获得更好的崩溃报告，这至少会告诉您托管异常发生的位置。
If you're unable to reproduce the problem yourself, I'd suggest rebuilding your app with Xamarin.iOS 7.0.6 (currently in the beta channel), and resubmit to Apple. The app may still crash, but you should get better crash reports which will at least tell you where the managed exception is occurring.
这篇关于无法复制Apple iOS app评论崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
