title: App rejected due to non reproducible bug: possible reasons?
body: <p>One of our apps recently got rejected for the second time, because "We found that your app failed to launch on iPad running iOS 6.0.1, on both Wi-Fi and cellular networks".</p>
  
  <p>The crash log provided by Apple starts with:</p>
  
  <blockquote>
    <p>Incident Identifier: CE8868A8-1C68-4161-91AD-DB50D3D5780B<br>
    CrashReporter Key:   83b816533ead866666681b87f5736242d8aac2ff<br>
    Hardware Model:      xxx<br>
    Process:         Test Skis [29192]<br>
    Path:            /var/mobile/Applications/890E8D9C-6A17-4EA6-9A06-5503B3D35888/Test   Skis.app/Test Skis
    Identifier:      Test Skis<br>
    Version:         ??? (???)<br>
    Code Type:       ARM (Native)<br>
    Parent Process:  launchd [1]  </p>
    
    <p>Date/Time:       2013-01-04 19:24:52.667 -0800<br>
    OS Version:      iOS 6.0.1 (10A523)<br>
    Report Version:  104  </p>
    
    <p>Exception Type:  EXC_CRASH (SIGABRT)<br>
    Exception Codes: 0x0000000000000000, 0x0000000000000000<br>
    Crashed Thread:  0  </p>
  </blockquote>
  
  <p>My question is not about how to fix the problem in our specific code, but a more general one: we have been unable to reproduce the crash using the same binary (making an Ad Hoc version), device, and OS version as the one Apple is supposedly using.</p>
  
  <p>How is it possible that such a crash occurs on the Apple reviewer's device, and not ours? Are Apple reviewers' devices configured in a non standard way that could explain the difference?</p>
  
  <p>I have found another question on Stack Overflow mentioning a similar issue, which has not been answered as well: <a href="https://stackoverflow.com/questions/10347091/apple-rejected-app-due-to-a-crash-which-is-not-reproducing">Apple rejected app due to a crash which is not reproducing</a> </p>