现在的位置: 首页 > 综合 > 正文

IPHONE – GSRegisterPurpleNamedPort SIGABRT in UIApplicationMain Before App Delegate Gets to Run Any Code

2017年10月31日 ⁄ 综合 ⁄ 共 1178字 ⁄ 字号 评论关闭

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

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.

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?

抱歉!评论已关闭.