在App Delegate获取运行任何代码之前，UIApplicationMain中的GSRegisterPurpleNamedPort SIGABRT [英] GSRegisterPurpleNamedPort SIGABRT in UIApplicationMain Before App Delegate Gets to Run Any Code

问题描述

我们最近对其中一个应用程序进行了更新，许多用户告诉我们他们无法再运行应用程序，因为它在启动时崩溃了。

We recently put an update out for one of our apps and many users told us that they could no longer run the app because it crashed on startup.

我们有能够通过在设备上构建和运行先前版本构建，然后在同一设备上构建并运行新构建版本来重新创建崩溃，但此崩溃的堆栈跟踪非常奇怪：

We have been able to recreate the crash by building and running the previous release build onto a device and then building and running the new build overtop of it on the same device, but the stack trace for this crash is very strange:

Thread 0 Crashed:
0   libSystem.B.dylib             0x000791d0 __kill + 8
1   libSystem.B.dylib             0x000791c0 kill + 4
2   libSystem.B.dylib             0x000791b2 raise + 10
3   libSystem.B.dylib             0x0008d6fa abort + 50
4   GraphicsServices              0x00003aa8 GSRegisterPurpleNamedPort + 172
5   GraphicsServices              0x00003d5a GSEventInitialize + 150
6   UIKit                         0x00004cd6 UIApplicationMain + 350
7   MyApp                         0x0000df5c main (main.m:14)
8   MyApp                         0x00002c84 start + 32

它似乎在主要调用的UIApplicationMain方法中崩溃。但它在到达我们的app委托中的任何方法之前崩溃了。我在所有app委托方法中都放置了断点，但没有达到它们。

It appears to be crashing in the UIApplicationMain method that main calls. But it crashes before it reaches any of the methods in our app delegate. I have put breakpoints in all of the app delegate methods and none of them are reached.

此外，这似乎只发生在更新应用程序的用户身上。从应用程序商店下载它而没有在iPhone上的用户没有看到问题。

In addition, this appears to be only occurring for users that are updating the app. Users that are downloading it from the app store without it already being on their iPhones are not seeing the problem.

有没有人遇到这样的崩溃？为什么这个问题只会发生在更新中？

Has anyone ever encountered a crash like this? Why would this problem only occur for updates?

推荐答案

这是在iOS 4.0下吗？据报道，当此应用程序的上一次安装中的进程或线程崩溃并且某些操作系统尚未清除或已在调试器中挂起时，会发生此类错误。

Is this under iOS 4.0? This type of error had been reported to occur when a process or thread from the previous install of this app has crashed and somehow hasn't been cleaned up by the OS yet or has hung up in the debugger.

在安装新版本的应用程序后重新启动iPhone会导致此错误消失吗？这将是一个很好的迹象，表明操作系统中的某些东西在之前的安装中被卡住/损坏，而不是在应用程序包本身中。

Does a reboot of the iPhone after installation of the new version of the app cause this error to go away? That would be one good indication that something is stuck/corrupted in the OS from the previous install, rather than in the app bundle itself.

这篇关于在App Delegate获取运行任何代码之前，UIApplicationMain中的GSRegisterPurpleNamedPort SIGABRT的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！