Hi, We recently migrated our iOS app icon to use the new 'single size' feature in xCode 14. However upon submission to App Store Connect we are getting the following issues: ITMS-90892: Missing recommended icon - The bundle does not contain an alternate app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleicons ITMS-90892: Missing recommended icon - The bundle does not contain an alternate app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleicons Is this something we should be worried about? Cheers, Walter

Hi, runningSpeed is now available as an HKQuantityTypeIdentifier in HealthKit in WatchOS9. However, when testing out our application on an Apple Watch Series 4 there is no data being returned even though the Watch is on WatchOS9. Is this expected behaviour or a bug? The docs (https://developer.apple.com/documentation/healthkit/hkquantitytypeidentifier/3929731-runningspeed/) say that it should be available on devices that support WatchOS9. Thanks, Walter

Hi, We recently launched an Apple Watch extension to our iOS, however, we are struggling to get crash reports from App Store Connect. We've had multiple reports from our users that the app has crashed while recording a workout (our watch app allows users to record a running workout) but cannot see any crash reports in app store connect. We've also added Crashlytics to try to get the crash reports but that too fails to log the crashes. Are there known issues with Crash reporting and WatchOS? Or do we need to enable some sort of configuration to get it working correctly? Also, one thing to add is that we are using swiftUI. This is starting to become a big blocker for us as we are finding it very difficult to debug the crashes from our users. Thanks, Walter