Unfortunately, the developers I've worked with have been unable to reproduce the crash by doing this. This rules out many issues related to the Debug or Release configurations being different in some way. You can test an archived build by "Share…"-ing an ad-hoc signing with yourself and finally submit *that exact same build* through the Organizer window. Normally what I recommend in these cases is to use Xcode 4's "Archive" feature. Unfortunately, I can't think of any way to simulate that on your end. The problem may be related to code-signing or the "ingestion" of the binary to the App Store. I am not aware of any differences in App Review's test environment that could be causing this issue. > and installs that would explain these inconsistencies? > Failing that, is there any difference in the way the review team tests It will also make it easier for you to track the status of the problem. This will let engineering know that more people are running into the issue. You might want to mention that it is a probably duplicate of rdar://problem/9231829. I can't recommend any other work-arounds, but as you said, several developers have had success using the Xcode 3.2.5 and iOS SDK 4.2 It's not yet clear exactly what is causing the problem, but it seems to be related to: Ip: 0x00000000 sp: 0x2fdffa44 lr: 0xffffffff pc: 0x00bc2084Īpple is aware of this issue and is still investigating it.
0 kommentar(er)
