What's new in watchOS 8

RSS for tag

Discuss the WWDC21 session What's new in watchOS 8.

View Session

Posts under wwdc21-10002 tag

18 Posts
Sort by:
Post not yet marked as solved
0 Replies
121 Views
I do not receive text notifications on my phone when wearing my watch. It is super frustrating. I am also not feeling haptics or hearing any notifications on my watch. This needs to be resolved and has not always been the case.
Posted
by Fam1.
Last updated
.
Post not yet marked as solved
0 Replies
339 Views
Hi I want to use the Close Your Ring apple watch app data into my app. Is there any way to save our apple watch data into our database to use it into IOS Apps. I want to save the data when the ring is completed. Please recommend any blog or tutorial to use the Apple Watch Close Your Ring app data into our IOS App. Thanks 😊 :)
Posted Last updated
.
Post not yet marked as solved
0 Replies
320 Views
Anyone know how to switch sleep focus mode off? I’ve set the schedule time it comes on at that time but won’t switch off at the set time, just stays on, on the phone and the watch. What’s the point of scheduling if it won’t switch off at the set time only switches on? Am I missing something?
Posted
by Me-.
Last updated
.
Post not yet marked as solved
0 Replies
480 Views
What's the API to trigger region base user notification on watchOS? I look at this document https://developer.apple.com/documentation/usernotifications/unlocationnotificationtrigger and seems like the functionality is available since watchOS3. Is there a new API instead?
Posted
by ethanfan.
Last updated
.
Post marked as solved
2 Replies
568 Views
I just updated my app for the always-on screen and watchOS 8. I mainly used the simulator while testing, but when I tested the app on the device the always-on screen behavior the same as for watchOS 7. When I updated my minimum deployment target to watchOS 8 the always-on screen was working. Is this feature not backwards compatible at all? Does it require the app to be compiled for watchOS 8 or is there any option to support watchOS 6 & 7 as well? I used Xcode 13 RC for testing this. In the article Designing Your App for the Always On State it states: Apps compiled for watchOS 8 and later have Always On enabled by default. You can disable this feature by setting the WKSupportsAlwaysOnDisplay key to false in the WatchKit Extension’s Info.plist file. Users can also disable Always On for the entire device or on a per-app basis by choosing Settings > Display & Brightness > Always On. It could be interpreted as: It needs watchOS 8 as a deployment target and in it works when you use Xcode 13 with the watchOS 8 toolchain
Posted
by AlexSFD.
Last updated
.
Post not yet marked as solved
1 Replies
326 Views
What do I need to do as I am getting a n error saying There is no Device registered in your account on the developer Website. Plug in and select a device to have the Xcode register it
Posted Last updated
.
Post marked as solved
2 Replies
584 Views
I have a watch app which is receiving location updates every second, so it is being executed in the background even if the wrist is down. I thought this would qualify the app to update the user interface every second, but it is not working. I set a breakpoint where the user interface is updated, and the code is being executed but I get no update in the user interface. I have tested this both in the simulator and in the device. Should this work with an app which gets locations updates? I thought it would make sense for an app like this. The app is written in objective-C if that makes it any different. Thank you.
Posted Last updated
.
Post not yet marked as solved
0 Replies
328 Views
I get this error sometimes It seems to fly while the screen moves, but I couldn't find the exact cause. When will this error occur? Incident Identifier: 62392CA5-B5A5-4C0A-A2DA-4B9CEF0F90C5 Hardware Model: iPhone8,1 Process: simkoong [813] Path: /private/var/containers/Bundle/Application/A9C0B266-832E-465C-A0AC-109B42ECC69A/simkoong.app/simkoong Identifier: com.colondee.simkoong Version: 1.0.0 (4.26.4) AppStoreTools: 12E506 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.colondee.simkoong [700] Date/Time: 2021-08-31 14:14:36.2055 +0900 Launch Time: 2021-08-31 14:08:16.4793 +0900 OS Version: iPhone OS 14.7.1 (18G82) Release Type: User Baseband Version: 8.80.01 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x18fea725c __exceptionPreprocess + 216 (NSException.m:199) 1 libobjc.A.dylib 0x1a3c3c480 objc_exception_throw + 56 (objc-exception.mm:565) 2 CoreFoundation 0x18fda8ba0 +[NSException raise:format:] + 108 (NSException.m:155) 3 UIKitCore 0x19208aafc -[UIViewController _addChildViewController:performHierarchyCheck:notifyWillMove:] + 304 (UIViewController.m:4407) 4 UIKitCore 0x19250a368 -[UIInputWindowController changeToInputViewSet:] + 616 (UIInputWindowController.m:2778) 5 UIKitCore 0x1925053c0 -[UIInputWindowController moveFromPlacement:toPlacement:starting:completion:] + 640 (UIInputWindowController.m:1862) 6 UIKitCore 0x19250b1e4 -[UIInputWindowController setInputViewSet:] + 1580 (UIInputWindowController.m:2968) 7 UIKitCore 0x192504da8 -[UIInputWindowController performOperations:withAnimationStyle:] + 52 (UIInputWindowController.m:1756) 8 UIKitCore 0x1921deac4 -[UIInputResponderController setKeyWindowSceneInputViews:animationStyle:] + 2460 (UIInputResponderController.m:1480) 9 UIKitCore 0x1921de104 -[UIInputResponderController setInputViews:animationStyle:] + 232 (UIInputResponderController.m:0) 10 UIKitCore 0x1921df5ac -[UIInputResponderController setInputViews:animated:] + 96 (UIInputResponderController.m:1536) 11 UIKitCore 0x1921df614 -[UIInputResponderController setInputViews:] + 76 (UIInputResponderController.m:1541) 12 UIKitCore 0x1921dcfcc __74-[UIInputResponderController _reloadInputViewsForKeyWindowSceneResponder:]_block_invoke.657 + 36 (UIInputResponderController.m:1052) 13 UIKitCore 0x1921dcb58 -[UIInputResponderController _reloadInputViewsForKeyWindowSceneResponder:] + 4016 (UIInputResponderController.m:1085) 14 UIKitCore 0x1921dbb8c -[UIInputResponderController _reloadInputViewsForResponder:] + 160 (UIInputResponderController.m:0) 15 UIKitCore 0x1927844c8 -[UIResponder(UIResponderInputViewAdditions) reloadInputViews] + 128 (UIResponder.m:1575) 16 UIKitCore 0x19277fcc8 -[UIResponder becomeFirstResponder] + 812 (UIResponder.m:357) 17 UIKitCore 0x191c82570 -[UIAlertController viewWillAppear:] + 232 (UIAlertController.m:2137) 18 UIKitCore 0x19208bf88 -[UIViewController _setViewAppearState:isAnimating:] + 604 (UIViewController.m:4864) 19 UIKitCore 0x19208c70c -[UIViewController __viewWillAppear:] + 116 (UIViewController.m:4989) 20 UIKitCore 0x191f79ce0 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke.466 + 1248 (UIPresentationController.m:1105) 21 UIKitCore 0x192bebee4 -[_UIAfterCACommitBlock run] + 64 (_UIAfterCACommitQueue.m:122) 22 UIKitCore 0x19275b9c4 _runAfterCACommitDeferredBlocks + 296 (UIApplication.m:2936) 23 UIKitCore 0x19274ae90 _cleanUpAfterCAFlushAndRunDeferredBlocks + 200 (UIApplication.m:2914) 24 UIKitCore 0x19277c1e0 _afterCACommitHandler + 76 (UIApplication.m:2970) 25 CoreFoundation 0x18fe25540 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 32 (CFRunLoop.c:1799) 26 CoreFoundation 0x18fe1fb70 __CFRunLoopDoObservers + 588 (CFRunLoop.c:1912) 27 CoreFoundation 0x18fe2010c __CFRunLoopRun + 1012 (CFRunLoop.c:2953) 28 CoreFoundation 0x18fe1f7d0 CFRunLoopRunSpecific + 572 (CFRunLoop.c:3242) 29 GraphicsServices 0x1a6561570 GSEventRunModal + 160 (GSEvent.c:2259) 30 UIKitCore 0x19274c2d0 -[UIApplication _run] + 1052 (UIApplication.m:3269) 31 UIKitCore 0x19275184c UIApplicationMain + 164 (UIApplication.m:4740) 32 simkoong 0x1049f834c main + 88 (main.m:14) 33 libdyld.dylib 0x18fafe140 start + 4 Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001bbd0d7b0 __pthread_kill + 8 1 libsystem_pthread.dylib 0x00000001d84b09c0 pthread_kill + 212 (pthread.c:1582) 2 libsystem_c.dylib 0x0000000198adeac0 __abort + 124 (abort.c:155) 3 libsystem_c.dylib 0x0000000198adea44 abort + 132 (abort.c:126) 4 libc++abi.dylib 0x00000001a3d16be8 abort_message + 128 (abort_message.cpp:78) 5 libc++abi.dylib 0x00000001a3d08d14 demangling_terminate_handler() + 296 (cxa_default_handlers.cpp:67) 6 libobjc.A.dylib 0x00000001a3c1c9a0 _objc_terminate() + 124 (objc-exception.mm:701) 7 FirebaseCrashlytics 0x000000010633fd28 FIRCLSTerminateHandler() + 332 (FIRCLSException.mm:335) 8 libc++abi.dylib 0x00000001a3d16074 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59) 9 libc++abi.dylib 0x00000001a3d18c18 __cxa_rethrow + 144 (cxa_exception.cpp:616) 10 libobjc.A.dylib 0x00000001a3c3c5d0 objc_exception_rethrow + 40 (objc-exception.mm:604) 11 CoreFoundation 0x000000018fe1f8bc CFRunLoopRunSpecific + 808 (CFRunLoop.c:3257) 12 GraphicsServices 0x00000001a6561570 GSEventRunModal + 160 (GSEvent.c:2259) 13 UIKitCore 0x000000019274c2d0 -[UIApplication _run] + 1052 (UIApplication.m:3269) 14 UIKitCore 0x000000019275184c UIApplicationMain + 164 (UIApplication.m:4740) 15 simkoong 0x00000001049f834c main + 88 (main.m:14) 16 libdyld.dylib 0x000000018fafe140 start + 4
Posted
by thpark.
Last updated
.
Post not yet marked as solved
0 Replies
270 Views
How do i install iMac Fusion Drive - 10.13 Beta Program
Posted
by Joseph55.
Last updated
.
Post not yet marked as solved
0 Replies
254 Views
Hello, I would like to ask you if you have problems like me and if you know how to solve them or if it is a bug beta version of IOS 15 and watchos 8. The first problem is with calls. When I call someone over a classic call and someone calls me, I don't see that someone called me when I called someone. And I have a second problem. When someone calls me in the latest beta version of watchos 8, they don't even show me the call on the watch. Thank you for answer.
Posted
by tucnacik.
Last updated
.
Post not yet marked as solved
0 Replies
536 Views
Hey! I would like to incorporate background delivery for my standalone Apple watch app by updating my Watch App Complication in a more timely manner compared to the scheduleBackgroundRefresh. While the documentation states that the query should be executed in application(didFinishLaunchingWithOptions:), this wouldn't work in this case as the App might not be opened. So I register the background delivery whenever the Extension Delegate handle() is called with a WKApplicationRefreshBackgroundTask. However this only works whenever I debug the App on the Device... As soon as I stop debugging the App, the Complication is only updated through a scheduled Background Refresh. I did enable the Background Delivery Capability & made sure that I didn't exceed the WKApplicationRefreshBackgroundTask budget — I'm currently testing on Beta 5. Thanks a lot for any insights in advance!
Posted Last updated
.
Post not yet marked as solved
1 Replies
473 Views
Hello, I am a physician. I have very little coding experience, but am able to learn. I am interested in potentially using apple watch in a small pilot project. In this project, the watch would be given to patients in a rural facility. I would like to remotely monitor these patients health data (heart rate, HRV, O2 saturation) by designing an apps that imports this data to a pre-existing Electronic Medical Record. Important note, these patients likely will NOT have an iPhone. Is this concept possible? Thank you for answering my question
Posted Last updated
.