I sure am missing something obvious here - but no matter where I looked I found nothing to aid me here so I'll give it a try:
I'm developing an (obj-c) app in wich I have integrated the Fabric / Crashlytics framework and wich I distribute to my testers via the fabulous Fabric-Site. That worked flawless for many, many versions. Now I have added AppleWatch-compatibility to my app via integration of WatchKit. All works fine.
But distribution via Fabric to my beta-testers just won't work any more; The distributions site just states "You're all set for now. As soon as a new Build is ready..." and under "Previous Versions" all version including the WatchKit are marked as "Not Available". Older versions are available to install though...
I suspect something wrong with the included provisioning profiles - but all are set up as they should - f.e. all devices registered in all profiles, separate profiles for the watch app and the extension - and the archives are created without errors or warnings. They even pass the AppStore validation. But no luck in getting those versions to my beta-testers...
Any hint would be much appreciated.
As at current date it continues to appear to be the case that WatchKit Apps and Extensions cannot be distribute by Fabric. The Fabric Documentation does not refer to WatchKit, WatchOS or Apple Watch at all, and the current only significant discussion of the question in the developer forums, from about five months ago, states it was not possible at that time.
来源：https://stackoverflow.com/questions/33062496/crashlytics-fabric-distribution-of-watch-enabled-ios-app