I have tried URL session requests in the following three ways: Proxy through iPhone: Request failure "ErrorDomain =NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." Connecting to a known network: Request successful Connecting using cellular data: Request successful These tests were all conducted on the Apple Watch Series 6 watchOS 9.4. Does "watch-only App "not support URL session request through iPhone Proxy? Here is my current URL session request handler: let config = URLSessionConfiguration.ephemeral config.waitsForConnectivity = true config.requestCachePolicy = .reloadIgnoringLocalCacheData config.urlCache = nil config.allowsCellularAccess = true config.allowsConstrainedNetworkAccess = true config.allowsExpensiveNetworkAccess = true let session = URLSession(configuration: config, delegate: nil, delegateQueue: .main) let task = session.dataTask(with: url) { (data, response, error) in guard error == nil else { print(error!) self.error = "\(error!)" return } } task.resume() Info.plist <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key> <true/> <key>NSAllowsLocalNetworking</key> <true/> </dict>

Hello, I tried to use the new underwaterDepthPrompt and underwaterDepthCriticalPrompt with WKInterfaceDevice.current().play(_:) without any success on my A2157/WatchOS 9.5.1 (others are working perfectly). Is it normal?

Hi there, I'm trying to figure out how to make my app always on top when waking the apple watch, just like the native Workout app does. I've noticed the official guidance for users to enable this behavior, but how can I introduce it into my own app? Any answers will be appreciated! Reference to apple support: https://support.apple.com/en-sg/guide/watch/apd748b87e2a/watchos -> Wake to your last activity

Hi, I just want to confirm that is it possible to make/receive VoIP calling through Apple Watch without pairing with iPhone

Hello, I'm having a problem on my watchOS app where even though I have instantiated a WKExtendedRuntimeSession the app stops logging IMU data a few seconds after the watch has gone to sleep. This happens on my Apple Watch Series 6, but does not happen on the latest Apple Watch Series 8. CPU usage in both cases does not exceed 70%, so I doubt my app is exceeding the limits thus cancelling the WKExtendedRuntimeSession. To back that up, I am not getting the WKExtendedRuntimeSessionInvalidationReason trigger I was suggested to put in place form the documentation. I have tested a couple of different sample rates, this does not seem to happen with a sample rate as low as 1, but does happen already with a sample rate of 30. Could it be a watch limitation, or am I forgetting something? P.S. I have also set the background mode to physical therapy and ticket the workout processing box.

Hello, I would like to built a phone app (or watch app if it is easier) to get raw data of ECG, spO2, accelerometer... Is it possible with all phone and watch models? Any recommandation ? I am looking for updated feedback compared to this one for instance https://academic.oup.com/sleep/article/42/12/zsz180/5549536 Thanks

I have an iPhone 14 Pro and Apple Watch SE. My phone is connected via Bluetooth to my car (it is NOT CarPlay). This feature has been working for at least a couple of iOS versions, however, I'm currently running iOS 17 Public Beta and WatchOS 10 Public Beta. When I start my car, my watch tells me how far I'm from home and if it's light/heavy traffic. As far as I can tell, Apple Maps is telling me this info. I do have Google Maps installed as well, but don't think it's that. This is NOT the "Find my car" feature. I recently moved (in the last few days) and updated my "Home" on both Apple Maps and Google Maps, however, when I start my car from my new address, it tells me how far I am from my old address. When I'm away from both addresses it still tells me the old address as well. I need to figure out how to update the new address so it'll tell me that distance when I start my car.

Hello everyone. My app has been rejected in App Store review multiple times due to improper use of HKWorkoutSession, but I see no way around this, and I haven't gotten any feedback from Apple telling me how I can get around this, they just say to remove it because the intended use of HKWorkoutSession is to read fitness data, which they say I am not doing. My app is designed to help induce lucid dreams, and it uses constant heart rate readings to do this. It reads the user's heart rate throughout the night (that is, the app is running for around 8 hours). Thus it needs to run as the frontmost app, and it needs to run for 8 hours continuously without user input. The only way I know of to do this is by using HKLiveWorkoutBuilder and HKWorkoutSession. Extended run time sessions do not work because of the 1 hr time limit. I would really appreciate any help with this problem. It is frustrating that Apple's review is providing no suggestions and will not accept my app if it uses HKWorkoutSession, which is essentially the backbone of the app. Thank you.

After all these years I'm STILL getting this message. WHY hasn't Apple fixed this yet?! I'm on version Version 14.3.1. Is there any way to get this working? Developing for Apple Watch has been a total nightmare from day 1, I don't understand how it hasn't gotten any better. This error keeps me from testing my app on my Watch. My Watch is obviously unlocked. I tired every troubleshooting step I've read in the dozens of other posts about this issue.

Hi, Is it possible to turn on airplane mode on watchOS using swift? or possible to know the state of airplane mode? thank you

Hi, I'm deploying my app to the store for the last several year. I have a Watch app. No matter what I do, I get the next warning above my version information screen for each new build: You’re currently using Apple Watch Series 3 screenshots for your latest watch build. Adding screenshots for the newest devices can help you accurately represent your app’s user experience on the App Store Although I take the screenshots on a real Watch series 9. Does anyone know how I solve it?

I've encountered a significant sync issue with watchOS 10 RC on every device combination I've tested, running both iOS 17 and watchOS 10. I'm curious if others have noticed a similar problem. Context: Standalone watchOS app developed in SwiftUI with a companion iOS app. Both apps use NSPersistentCloudKitContainer for bi-directional CloudKit CoreData Sync between the iOS app and watch. Previously, this sync mechanism was near instant in the foreground and took max 1-2 minutes in the background NSPersistentCloudKitContainer has been reliable since the app was first developed in the watchOS 6/iOS 13 era. Issue: In watchOS 10 RC, sync can take hours--and doesn't even occur when the app is in the foreground. Sync only reliably happens when the watch is placed on the charger, seemingly only if the charge is over 50%. Once taken off the charger, the watch will continue push and receive CoreData changes briefly before becoming unresponsive to sync again. Additional Info: The problem persists even when recompiled with the latest Xcode RC. It's problem is consistent in both production and development CloudKit environments. The CloudKit log shows no watch activity upon CoreData object updates, until placed on the charger (with over 50% charge). The sync starts in the background while the watch is charging. The iOS app, however, reflects immediate activity in the CloudKit log after a CoreData change from the device and reacts promptly to pushes when they eventually occur from the watch. The NSPersistentCloudKitContainer code hasn't changed since it was implemented. Background modes for remote notifications are set correctly, and when sync finally happens, it's accurate. I'm stumped. Perhaps there's a new watchOS 10 setting affecting CloudKit sync QoS? Or could this be a known watchOS 10 RC bug?

Has someone else already noticed a massive battery drain under the stable version of WatchOS 10? Normally I had about two full days of battery life on my Watch SE2. And now I barely got one day of battery life. Hopefully a fix is rolled out soon.

Hi, I'm the developer of Open Water Swim, and I have had multiple reports and have also confirmed with my own testing that the WatchOS 10 update has seriously degraded GPS data during open water swimming, both with the native Workout app and with Open Water Swim. The data provided by CoreLocation is no longer accurate or trustworthy. I will post several pictures showing before and after update swims: Here's the raw data (mapped) of a swim done with watchOS 9 on the Ultra. Same swim today: From another pair of users: These two went TOGETHER, one with watchOS 9 and one with watchOS 10. You can probably guess which is which. Watch OS 9 swim: SAME SWIM WITH A PARTNER ON WATCHOS 10 (beta here) And another, again, two people swimming together, one watchOS 9 and one watchOS 10. watchOS 9 Same swim, same time, watchOS 10 I have filed two feedback assistant reports with APPLE. One when it was still a beta issue: FB12587468. This one has zero response from apple. And now a second one filed with watchOS 10 release: FB13192409 Apple devs, I know you're here and listening, so please let's get this fixed ASAP. Thanks

I am unable to get past pairing with apple watch without signing in using apple id to connect messages to the watch but cant sign in with apple id because the watch is not updated but the watch cannot update because it is too old (series 3). And it did do an update when I first paired it. And now it's not attempting to update anymore. And there is no way to access settings on the watch. And there seems to be no way around the messages apple Id screen.

Hello, I'd love to know if there's a way to prevent people from sharing my custom .watchface files. I know it's easy to share them, what I want to know is if there's any way to prevent it (such as licensing my creations or any way I couldn't think of). Thank you!

Has anyone else seen this issue? When the Action Button on an Apple Watch Ultra 2 is connected to a Shortcut, it seems to run the shortcut twice. I'm on watchOS 10.0.2. A user of an app I built reported the issue, which is how I knew about it in the first place. I'm wondering if it's an issue on my watch specifically, or if many other people are seeing the same thing. I replicated the issue using a fresh project, and it only seems to happen when the shortcut responds with dialog. Does anyone know why this is happening and how to fix it? The shortcut with a dialog response works fine everywhere else, and only exhibits this behavior when run with the Action Button. Here is the full code with instructions to replicate the issue, so I'm curious if other people see the same thing: // When running a shortcut that returns dialog // with the Apple Watch Ultra Action Button, // the shortcut runs twice. // Create a new iOS project and add this: import AppIntents // AppIntent struct LogEventNow: AppIntent { static var title: LocalizedStringResource = "Log an Event" @MainActor func perform() async throws // -> some IntentResult // When just returning a successful result with .result(), // the shortcut only runs once as expected // Add ProvidesDialog to be able to return .result(dialog:) -> some IntentResult & ProvidesDialog { let loggedDate = Date() let formattedLoggedDate = loggedDate.formatted(date: .omitted, time: .complete) // Print the time of the event that was logged print(formattedLoggedDate) // This gives the expected result // Shortcut runs once, and prints one time to the console // return .result() // This gives unexpected result // Shortcut seems to run twice // and prints two date a 1–2 seconds apart return .result(dialog: "Successfully logged.") } } // AppShortcut // This makes it show up in the Shortcuts app struct EventShortcuts: AppShortcutsProvider { static var appShortcuts: [AppShortcut] { AppShortcut( intent: LogEventNow(), phrases: ["Log in \(.applicationName)"], shortTitle: "Log Event Now", systemImageName: "calendar" ) } } // Steps to reproduce the issue: // - Long press the AppShortcut in Shortcuts app // - Tap "Add to Shortcut" // - Tap the "i" at the bottom // - Turn on "Show on Apple Watch" toggle // - Open the Watch app on iPhone // - Tap "Action Button" // - Under "Action" choose "Shortcut" // - Select the Shortcut that was created in the Shortcuts app // - Push the Action Button and observe two dates printed to the console // Sometimes I'm also seeing "Remote execution timed out" on Apple Watch a minute or so after the shortcut has run, but only when leaving the Shortcuts app open after it runs from the Action button.

Apple Watch 6 iOS 10.1 - Keynote Remote via iPad mini 6 iPadOS 17.1 - Keynote Presentation I can connect my iPhone with the Keynote Remote on my MacBook Pro and my iPad Mini for Keynote presentations. All devices sync perfectly when I use my Apple Watch 6 to advance to the next slide. This setup works seamlessly over WiFi. With the new iOS 17 on my iPad Mini 6, which has a USB-C port, I can directly connect an HDMI adapter to an HDTV. This also works well. However, I'm facing an issue when trying to use my Apple Watch 6 as a Keynote Remote for my iPad Mini presentation. The Apple Watch doesn't seem to support a direct standalone connection with the iPad Mini for this purpose. Is there a solution for using the Apple Watch as a Keynote remote for the iPad Mini when it's connected to an HDTV? This should be part of #AccessibilityLens in it. Thank you,