GSRegisterPurpleNamedPort SIGABRT 在 UIApplicationMain 在应用程序委托开始运行任何代码之前 [英] 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

它似乎在 main 调用的 UIApplicationMain 方法中崩溃.但是它在到达我们的应用程序委托中的任何方法之前就崩溃了.我在所有应用程序委托方法中都设置了断点，但都没有到达.

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.

这篇关于GSRegisterPurpleNamedPort SIGABRT 在 UIApplicationMain 在应用程序委托开始运行任何代码之前的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！