Info watchOS: 11.0 (22R5348a) *Though has been present since watchOS 10. Issue: Other apps playing music cancel out WKHaptics from firing (low volume and no vibrations) Description When another app is playing music (ex: spotify) in the background while using my app, that uses WKHaptics. The WKHaptics vibrations are non existent as long as headphones are connected. When the headphones are disconnected the vibrations return. Test MVP test app >> https://github.com/mazefest/AppleCodeSupportTestApp

I'm trying to download the watchOS 8.5 runtime simulator to Xcode 15.2 but it has failed probably 5 times. Saying something failed during installation. I decided to just download it directly here https://developer.apple.com/download/all/ but it is not available. Why is that? Thanks

I have an app that is stuck in Ready For Distribution. App Store Connect is not showing the Distribute Button, and there is no way to pull the build down to re submit. Is anyone else experiencing this issue?

Is anyone else unable to select 'add existing user' and then add a user to a testing group. When i select 'add existing' user, all users are grayed out and not selectable.

I have an app that supports AOD, after updating my device from wOS 8 to latest wOS9 beta AOD no longer works as expected, acting as if it is not enabled. Is anyone else experiencing this, I have the "WKSupportsAlwaysOnDisplay" set to true in the WKExtension Plist.

Is there a way to separate the tones and vibrations when using WKHaptics. This is the only way to play vibrations as far as I know for the Apple Watch. I'm trying to find a way for users to input settings for tones/vibrations in the app to give more customizability, but right now using WKHaptics they seem coupled.

Why is this being required for a non tvOS app?

I am attempting to implement a refreshable list on the Apple Watch. It says it is supported in watchOS8. But I am unable to get this to work in the simulator. Is this not supported? Do I need to attempt to implement my own implementation? thanks

It seems that reloadRootPageControllers, stopped at initializing pages at start up? Is this normal, it looks like the Interface controllers don't initialize until you scroll to them. Is this expected? This mean I am unable to user functions like becomeCurrentPage() until after I scroll to that page.

I want to be able to change the value for "App Supports Always On Display (Watch)" from yes to no depending on a variable in the app. We are in the middle of migrating our code over to swiftui so that our app appropriately uses the AOD display. however our users voiced distain for the AOD fallback screen. So what we want to do is allow our beta testers to use the AOD feature by changing the value of the "App Supports Always On Display (Watch)" to true and for our production users keep it at false. Is this possible? Thanks

I've seen many threads like this one that state the following; We understand that you have questions about compatibility with the new iPhone 13 and Apple Watch series 2. iPhone 13 will run iOS 15. Your Apple Watch will need to run watchOS 8. watchOS 8 requires iPhone 6s or later with iOS 15 or later and one of the following Apple Watch models: Apple Watch Series 3 Apple Watch Series 4 Apple Watch Series 5 Apple Watch SE Apple Watch Series 6 Apple Watch Series 7 So fro, that answer I would say no, but then I find videos like this one online where people are able to pair Series 2 devices to iPhone 13. So is it compatible or not? and if so what limitations does the Series 2 have when working with iOS 15 devices.

My app needs the ability to communicate with bluetooth devices when the app is in the background. This was solved by going into my apps Plist file and adding App communicates using CoreBluetooth to the Required Background Modes. The app works as expected when this is added. Now when I attempt to upload my app I am given the following error:  Missing entitlement. watchOS extension 'company.app/Watch/AppName.app/PlugIns/AppName Extension.appex' uses 'UIBackgroundModes' value 'bluetooth-central' without the required entitlement 'com.apple.developer.bluetooth-central-background' signed into the bundle. I do not feel like this should be required, does anyone have an idea on how to solve this issue? Thanks

I Implemented the below function peripheral(peripheral didUpdateValueForCharacteristic:) Which is where I parse information from a bluetooth device that pairs with our app. Ever since wOS8 our app stops receiving these call when the app is put in the background. Why is that, and does anyone have a possible workaround? Thanks

I'm not sure what I'm missing, app is compiled with Xcode 13 and I got it to work awhile ago and now I keep getting the default blur/clock instead of the AOD. Am I missing something here, In the documentation (link) it states the following "Apps compiled for watchOS 8 and later have Always On enabled by default. "

I'm trying to create a Framework that I can use across platforms. I have successfully added the framework to a test app and this is what the test framework looks like. import Foundation public class HelloComputer {     public func getHello() -> String {         return "hello world"     } } But when I import the framework this is what happens Am I missing something? Why is it asking for a instance of its self?