I’m sitting on a rock,
minding my own business…
… when suddenly, they’re onto me.
Hello,
At this time, XXXX cannot be posted to the App Store because it is crashing on iPhone 3G running iPhone OS 3.0.1. Crash logs have been attached for your reference.
For more information regarding crash logs:
http://developer.apple.com/iphone/library/technotes/tn2008/tn2151.html
One look at the document and I have this empty feeling in my stomach.
… resolving stack trace addresses to source code methods and lines – requires the application binary that was uploaded to the App Store and the .dSYM file that was generated when that binary was built. This must be an exact match – otherwise, the report cannot be symbolicated. It’s essential that you keep each build distributed …
Nobody told me before about dSYM files or atleast I did not hear/read about it. And if its a common knowledge in this part of the world, well, before this, I was working under a rock, tinkering with protocols ..
While the good folks on internet here and here have already taken care of explaining in detail the debugging steps, I still required the dSym file.
It turned out, I had the build files after all for one of my app. I was also able to reproduce the problem by just following the instructions given in the mail.
But IMHO, the rejection mail is too late in the process to let me know that I may need the dSYM file. It can probably be mentioned in iTunes Connect Developer guide so that no one misses archiving the build in the last minute rush to release the app.
In case you did not save dSYM files, here are the options for you:
- Try reproducing the problem using the steps sent in the rejection mail.
- Run instruments or static analyzer tool to flush out any errors.
- If nothing else works, submit again, wait for 2 more weeks for Apple approval (or rejection) (of-course am kidding).