UIAlertView Causes Crash in iOS SDK 6.0

前端 未结 2 1662
青春惊慌失措
青春惊慌失措 2021-02-12 17:30

I recently submitted an app to App Store that has not been accepted yet. Meanwhile, I downloaded Xcode 4.5 and tested my app in iPhone 6.0 Simulator.

However, when I i

2条回答
  •  小鲜肉
    小鲜肉 (楼主)
    2021-02-12 18:19

    See this related Question: UIAlertView shown from background thread and with no delegate creates EXC_BAD_ACCESS

    User input and UI calls must come from the main thread. Many of them will work "most" of the time on other threads, but sometimes will crash. They are more likely to crash differently (more or less often) on a device than the simulator, but it's possible Apple made changes that affect that difference in iOS6.

    And to your second question, I would answer yes, I would upload an updated binary for review as soon as you fix the issue, especially if you can reproduce this on a device (I strongly encourage you to attempt to reproduce it on a device). Otherwise, you may A) get accepted with a bug your users hate, or B) get rejected and have a an even longer delay and possibly more scrutiny. If you send an updated binary before review finishes it does put you at the "back of the line" AFAIK, but better than the alternatives.

提交回复
热议问题