>What I would like to see is
Interesting comments, thanks for sharing, but asforum posts aren't bug reports, feel free to use the bug reporter/(suggestions) link below, adding your report # to your thread for ref., thanks.
>Right now my app works perfectly fine on 1 iOS device but another device some features are broken. We need to be able to tell what users are on what devices so it can aid us in fixing issue
That's what crash reports via ASC, and your own testing, are for, not store stats. If you're using just the store to test, you're doing it wrong.
>I'm frankly shocked Apple does not provide this yet they can tell us
It's only/always about the money, and the gold is in the stats...Apple shares only what is good for -their- bottom line, devs are just fodder towards that end. Nothing shocking about that equation, I think. Welcome to the App Store.
> We need to be able to tell what users are on what devices so it can aid us in fixing issues.
Apple has no way of knowing when a feature on your app is not working unless there is a crash. Your crash reports will describe the device and the iOS for each crash. For all other problems your app can detect the type of device and iOS and communicate that to you through your servers or through the CloudKit public database.
You could use a third-party analytics tool such as Fabric / Crashlytics. It won't tell you who installed your app due to privacy concerns (Apple would never allow collecting that kind of information) but it tells you on which types of devices and versions of iOS it was installed and how many new users are seen each day. It has hooks you can put into your code so you can see when a particular feature is used.