On an iOS device and all simulators, the application works fine, but when adding it to the App Store, it was rejected by answering:

2.1: Apps that crash will be rejected

We found your app crashed on review.

We have attached detailed crash logs for your reference.

It makes it necessary to revise your app.

If you’re interested in technical support. If you have crash logs, symbolicate crash logs before contacting Apple Developer Technical Support.

If you have difficulty reproducing this workflow, you can try testing the workflow with Xcode's Archive feature.

  • I suspect that 5s are not tested. 64bit ios is not the same as an emulator. I had a problem with type casting (in one library). - Yura Ivanov
  • the simulator is there, not the emulator - this is the main problem, the iOS simulator is actually iOs compiled libraries for x86-64 + a bit of hardware binding, unlike the android emulator that converts commands from the native ARM device to x86 - aknew

1 answer 1

Not enough information, below I will give my questions / assumptions, maybe a solution can be found among them:

  1. As far as I remember, the guys from Apple send the crash in that case, what's in it? Usually, it is clear what fell
  2. Did you check it only on simulators? A bad idea is that the simulator is not the same as the device, there are different binaries used and much cooler hardware. From what I've seen - there may be some codecs that are not in ayoshi, because of the settings of the desktop system, the names of files are not case sensitive, and the size of external memory is all hard and the RAM is a few gigs
  3. Did you check it on all versions of supported axes? Different methods are available in different versions of sdk, ixcode does not speak about this, but the application will fall in runtime
  4. Another possible option is that you all checked for the debug version, but somewhere there is something like #ifdef DEBUG #else and in the release another code
  5. Starting a program from ixcode usually leads to additional time spent on communicating with ixcode and transferring to it yanykogo data (logs and mn), he saw the option when something fell during such a start on timeout, but the same binary normally worked without ixcode (in I mean, I flooded the device onto the device, launched it from ixcode - it fell, launched it again just by clicking on it on the device - everything is OK, it was checked several times independently on several devices). You can reverse the situation - something has time to complete correctly or does not have time to interrupt due to the delay
  6. Ixcod likes to leave resources from the last launch on a simulator device, and it happens that the file is mistakenly deleted or the code for copying it is damaged, for example, into documents, but since This resource was copied to the device / to a specific place in the bundle on one of the previous launches when it all worked, the developer is fine, but starting from scratch will have problems. I even met such a problem with the students, and at the same time the two developers were fine, but I didn’t have it. I unloaded the project after unloading it and the old one left me. The private version is an old bug with localization, for example, when creating a new version of the localization file (* .strings or xiba), I persistently wrote in the project the absolute path to this file on a specific machine, after which it was not collected by anyone except the developer.
  • 1. Yes, there is such, 4 files with approximately the same name about the iPad: Tap Tap_2014-05-13-175459_ATL-iPad.crash application made only for the iPhone. 2. On the iPhone 5 more. 3. The application is only for iOS 7 and above. 4. That's vryatli. 5. Runs norms and through XCode and without it. 6. Removed completely from the device and started again - everything is ok. - 97mik
  • Here is the-balls.tk/Crash.zip - 97mik
  • 9 Foundation 0x0000 You have something not passed in [NSURL (NSURL) fileURLWithPath:], most likely nil instead of a line, from where it is jerking incomprehensibly, but most likely from application didFinishLaunchingWithOptions: - aknew
  • Well, I have only 2 sections of the code associated with the files: pp.vk.me/c616521/v616521663/e8c6/GiCvavnPiEg.jpg pp.vk.me/c616521/v616521663/e8ce/0yj_AMuSNFM.jpg - 97mik
  • one
    Honestly, in any case there shouldn't be a crash - in theory there are two paradigms of working with errors - either you throw an exception, or you return an error code or special object, and this method has NSError ** in the parameters, but everything falls in by ekspepshenu. If only somewhere inside the application something else is heavily stranded like NSURLProtocol - aknew