I appreciate you elucidating the experience of app reviewers, helpful to know how they may be undergoing the review process.With all due respect however, we obviously don't want to harm our large user base and that wasn't the question. Additionally, ambiguity in debugging is precisely what you do not want. A freeze at boot can be numorous things, including an issue with Apple's latest iOS release or a bug in their latest frameworks, which is something I'm curious other's have experienced. Shared experiences is what I'm curious of.Fundamentally, without either a locally reproducable case or without some detailed causal factors (from the reviewers or forums) you're left with wasted people hours shooting in the dark. Even the most defensively coded, precisely reviewed app cannot somehow supplant causal modeling.

Brigitte, as I've written earlier, I would like to fix the issue. We have tried throwing a ton of weight at the problem already and we'd simply like some clarification on device model and iOS version. For what reason would we be denied access to that information? Also, how could one conclude this affects millions of users without an actual explanation of the problem, which would be deduced by a combination of gathered information and testing over some device population?

We got in touch with a contact at Apple and they concluded it was indeed an issue from their end. The app has been subsequently re-reviewed and approved.

Thank you for whoever fixed it.