App Submission fails BUT BUG CANNOT BE REPRODUCED IN DEBUG MODE

Solar2D iOS
#1

Hi,

We are having this weird issue related to submitting our app on iOS. 

Basically when we build ( using developer profile ) and test ( via test flight ) everything works fine as expected even with most extensive test cases. 

But when build ( using iOS distribution profile ) and submitted to apple … in the review process it fails to pass due to a bug which we CANNOT REPRODUCE. 

So, my best guess is that the bug/error is only happening in the release build ( probably due to code optimisation ) … but I can’t even know where and what to look for if I can’t reproduce ?

I have submitted it the app twice so far ( with possible guess and fix ) and both time it came back with same error.

How do I test or even see the logs using a release build ? ( so far the DTS has been useless in providing any useful information )

PLEASE HELP. 

below is what we received from apple:

We found that your app exhibited one or more bugs, when reviewed on iPad running iOS 7.1.1 and iPhone 5s running iOS 7.1.1, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.

Specifically, your app loaded indefinitely.

Steps to reproduce:

  1. Launch the app
  2. Tap “OPEN”
  3. Tap “CLASS MODE”
  4. App displays a loading screen and no further action can be taken. A screenshot is attached for your reference

[sharedmedia=core:attachments:2498]

#2

  1. I would suggest using an AdHoc distribution build instead of a Developer Build.  It’s as close to a release build as you can get.  Then let your testflight users hit that and see if they can create the issue.

  2. You can ask Apple to provide you a console log from the run and see if you can see an error showing up.

Rob

#3

  1. I would suggest using an AdHoc distribution build instead of a Developer Build.  It’s as close to a release build as you can get.  Then let your testflight users hit that and see if they can create the issue.

  2. You can ask Apple to provide you a console log from the run and see if you can see an error showing up.

Rob