Apple Intelligence

RSS for tag

Apple Intelligence is the personal intelligence system that puts powerful generative models right at the core of your iPhone, iPad, and Mac and powers incredible new features to help users communicate, work, and express themselves.

Posts under Apple Intelligence subtopic

Post

Replies

Boosts

Views

Activity

New Siri Waitlist not activating on iPhone/iPad after 4 days — macOS workaround works but not syncing
Hi, I joined the New Siri waitlist on June 8 (the day of WWDC 2026) and as of June 12, I have still not been granted access on iPhone or iPad — that's 4 days with no activation. I used the Terminal workaround on macOS 27 Golden Gate Beta (EnhancedSiriWaitlist → Enabled = NO), which successfully activated New Siri on my Mac. However, it has not synced to my other devices despite being on the same Apple ID with iCloud Siri sync enabled. Device details: Mac mini (macOS 27 Golden Gate Beta) — New Siri active ✓ iPhone (iOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 iPad (iPadOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 Steps already attempted: Multiple restarts on iPhone and iPad Toggled iCloud Siri sync off/on Toggled Siri off/on multiple times iCloud storage sufficient (200GB plan, 53GB used) 4 days seems far beyond normal rollout time. Is this a known issue? Is there anything on the account side that could be blocking activation? Thank you.
0
0
459
Jun ’26
What is the correct way to modify a SceneStorage variable from an AppIntent to one scene only for iPad SplitView mode
Apple's sample code 'Trails' supports multiple scenes, however everything is using shared state across the scenes. Put the app in Split View mode and have two windows of the app running and navigate, you can see both mirror each other. Works as designed, it is using a shared 'navigation model' across all scenes. https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents I would like to know if there is a supported or recommended way to modify individual scene storage from within the perform body of an AppIntent. The objective is to have App Shortcuts that launch different tabs in a TabView or different selections in a List. In short, I want to deep link to features, but account for more than one scene being open on iPad and only have programatic navigation happen on the scene that is 'foremost' or the 'activated' one in Split View. I have it working with either a @Dependency or posting a Notification with my main ContentView listening to the other end, but it changes all scenes.
0
0
737
Aug ’24
Siri AI’s onscreen awareness can’t understand an AppEntity without a schema?
Use Case I’m currently developing , a hiking and cycling app. I’d like to use Siri AI in iOS/watchOS 27 to create an experience like this: While users are recording an activity in app, they can raise their wrist or invoke Siri on iPhone and simply ask: “How much farther to the destination?” “How far have I already gone?” “How much elevation gain is left?” “How far is it to the next waypoint?” … Siri can then answer based on the app’s current workout context. Since there are many metrics like these, and it’s not convenient to look at the screen while cycling or trail running, this could be a really valuable use case if Siri AI can support it. I defined an AppEntity like this, and then associated it with the UI. But I found that Siri AI doesn’t seem to understand this AppEntity. It can only understand the content it can see on the screen, even though I can see that it did execute ToobooWorkoutSessionQuery, the EntityQuery. This screen has multiple tabs. Siri understood the on-screen values such as “Distance: 0.21 mi” and “Remaining Distance: 0.14 mi”, but it didn’t know the data from the other tabs on the same page, such as heart rate, average speed, and so on. So it seems that Siri is directly reading the screen, instead of retrieving the information from the AppEntity I actually provided. Is this because the AppEntity doesn’t use one of the schemas defined by AppSchemaEntity, so Siri AI can’t understand it? App Intents without a schema seem to have a similar issue. If the AppIntent I define is not within one of those schemas, Siri won’t directly execute it either. My current solution: I defined many Intents and Shortcuts. Siri AI’s ability to parse shortcuts seems to be much smarter in the new system, and it can match them quite easily. Also, shortcuts don’t require the app to be in the foreground. However, when talking to Siri, the shortcut phrase has to include the app name, which feels a bit unnatural. For example: “How far have I traveled in xxx app?”
0
1
602
Jul ’26
Dependency between AssistantSchema.CameraEnum
Hi, I have some questions about the new AssistantSchema.CameraEnum.captureMode and AssistantSchema.CameraEnum.captureDevice introduced with iOS 18 beta 4. Here's the context. I create a intent: @AssistantIntent(schema: .camera.startCapture) struct StartCaptureIntent { var captureMode: CaptureMode var timerDuration: CaptureDuration? var device: CaptureDevice? func perform() async throws -> some IntentResult { .result() } } And these app enums: @AssistantEnum(schema: .camera.captureDevice) enum CaptureDevice: String { case front case back case ultrawide } @AssistantEnum(schema: .camera.captureMode) enum CaptureMode: String { case modeA case modeB } Some CaptureDevice cases are not available in some CaptureMode. e.g: CaptureMode.modeA only supports CaptureDevice.back and CaptureDevice.front. In a classic AppIntent, I would create an AppEntity to represent CaptureDevice and use @IntentParameterDependency<CapturePhotoIntent>( \.$captureMode) to create a dependency between the captureMode and the captureDevice parameters. How can we create this dependency between two @AssistantEnum? I'm not sure this is possible as @AssistantEnum creates AppEnum.
0
1
621
Jul ’24
Apple intelligence feature in macOS 15.1 beta software testing not working with compatible hardware and system settings
I am attempting to install the macOS 15.1 update alongside the Apple Intelligence beta feature, to experience and then integrate into my developing application. I have a compatible MacBook Air M2 with a regional designation of the United States and language as US English, but is however purchased in mainland China. i have downloaded 15.1 but apple intelligence does not display, is this arising from buying it in China?
0
0
839
Aug ’24
Is it possible to set writingToolsBehavior globally?
Hello, we're investigating an option to disable writing tools for some customers in our app. I'm aware of the writingToolsBehavior property for UITextView etc, but we would like to have a way to set this globally without having to update all UITextView instances (or future instances). Is there any API to do this? We tried using UITextView.appearance.writingToolsBehavior = .none and it seemed promising on 18.2 beta, however it introduced crashes on devices running 18.1. The crashes look like: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Have you sent -setWritingToolsBehavior: to <UITextView: 0x14462c000; frame = (0 0; 0 0); text = ''; userInteractionEnabled = NO; gestureRecognizers = <NSArray: 0x30067cb40>; backgroundColor = UIExtendedGrayColorSpace 0 0; layer = <CALayer: 0x3009b1ba0>; contentOffset: {0, 0}; contentSize: {0, 0}; adjustedContentInset: {0, 0, 0, 0}> off the main thread? To verify, look for a complaint in the logs: "Unsupported use of UIKit…", and fix the problem if you find it. If your use is main-thread only please file a radar on UIKit, and attach this log. exercisedImplementations = { "setWritingToolsBehavior:" = ( ); }' Similarly, even on 18.2 beta if we used UITextField.appearance.writingToolsBehavior = .none we would see crashes for any search fields like: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Have you sent -setWritingToolsBehavior: to <UISearchBarTextField: 0x141c04a00; frame = (0 0; 0 0); text = ''; opaque = NO; gestureRecognizers = <NSArray: 0x301fe15c0>; placeholder = Search Leads; borderStyle = RoundedRect; background = <_UITextFieldSystemBackgroundProvider: 0x3015de960: backgroundView=<_UISearchBarSearchFieldBackgroundView: 0x141c60200; frame = (0 0; 0 0); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x3015de8e0>>, fillColor=(null), textfield=<UISearchBarTextField: 0x141c04a00>>; layer = <CALayer: 0x3015de240>> off the main thread? To verify, look for a complaint in the logs: "Unsupported use of UIKit…", and fix the problem if you find it. If your use is main-thread only please file a radar on UIKit, and attach this log. exercisedImplementations = { "setWritingToolsBehavior:" = ( ); }' Is it possible to set this globally?
0
3
499
Nov ’24
How to test for VisualIntelligence available on device?
I'm adding Visual Intelligence support to my app, and now want to add a Tip using TipKit to guide users to this feature from within my app. I want to add a Rule to my Tip which will only show this Tip on devices where Visual Intelligence is supported (ex. not iPhone 14 Pro Max). What is the best way for me to determine availability to set this TipKit rule? Here's the documentation I'm following for Visual Intelligence: https://developer.apple.com/documentation/visualintelligence/integrating-your-app-with-visual-intelligence
0
0
953
Sep ’25
Writing tools options
Hi team, We have implemented a writing tool inside a WebView that allows users to type content in a textarea. When the "Show Writing Tools" button is clicked, an AI-powered editor opens. After clicking the "Rewrite" button, the AI modifies the text. However, when clicking the "Replace" button, the rewritten text does not update the original textarea. Kindly check and help me showButton.addTarget(self, action: #selector(showWritingTools(_:)), for: .touchUpInside) @available(iOS 18.2, *) optional func showWritingTools(_ sender: Any) Note: same cases working in TextView pfa
0
0
479
Mar ’25
just curious
hey just curious if apple intelligence will be available on iPhone 15 Plus as well??? in october or is there a way that iPhone 15 Plus owners can join apple intelligence’s wait lists or something??? please let me know !😫
0
0
319
Sep ’24
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1 I am seeing a reproducible issue in Apple Mail on macOS 27 Developer Beta 1 where the compose body becomes locked/uneditable after using Apple Intelligence writing tools. Environment Mac: macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q Device: MacBook Pro with Apple Silicon shouldSwitchToCampoMode: false (isEnhancedSiriAvailable=false) App: Apple Mail Compose window Apple Intelligence Writing Tools Summary When composing an email in Apple Mail, if I write some text and then use Apple Intelligence to rewrite it — for example using Friendly, Professional, or Concise — Mail replaces the original text with the rewritten version. After the rewritten text is inserted, the message body becomes unresponsive. I cannot continue typing, edit the rewritten text, delete text, select text normally, or add new content inside the email body. The Apple Intelligence button also becomes unresponsive after this happens. The only actions that still seem to work are sending the email, discarding the draft, or using some toolbar actions such as emoji insertion. Steps to Reproduce Open Apple Mail on macOS 27 Developer Beta 1. Create a new email. Type any text into the email body. Use Apple Intelligence Writing Tools. Choose a rewrite option such as: Friendly Professional Concise Let Apple Intelligence replace/update the email body text. Try to click back into the message body and continue typing or editing. Expected Result After Apple Intelligence rewrites the email body, the compose field should remain fully editable. The user should be able to: Continue typing after the rewritten text Edit or delete the rewritten text Select and modify text Use Apple Intelligence again on the updated content Continue composing the email normally Actual Result After Apple Intelligence inserts the rewritten text: The email body becomes uneditable. Typing no longer works inside the message body. Clicking inside the body does not restore normal editing. Existing text cannot be edited or changed. Apple Intelligence controls become unresponsive. The compose window itself does not fully crash, but the body editor appears stuck. Send and discard still appear to work. Reproducibility This appears to be reproducible after using Apple Intelligence rewriting tools inside Apple Mail’s compose window. It was working before, so this appears to be a regression in macOS 27 Developer Beta 1.
0
0
269
Jun ’26
ToolIntent experience on watchOS
ToolIntent is currently marked unavailable on watchOS. (FB25455121) When Siri is invoked on Watch, what behavior(s) can users expect when invoking ToolIntents declared in our paired iOS codebase? Example use case: At their gym, a user leaves their iPhone face down nearby. To Siri on their Watch, they say "I just did 350 lbs 8 reps to failure" or "Rest for 3 minutes" or "Hack squat machine is busy, let's jump to the next exercise". If it matters, we benefit from extended background runtime via a mirrored live HKWorkout between our watch app and iPhone app (which displays a Live Activity).
0
0
267
1w
New Siri Waitlist not activating on iPhone/iPad after 4 days — macOS workaround works but not syncing
Hi, I joined the New Siri waitlist on June 8 (the day of WWDC 2026) and as of June 12, I have still not been granted access on iPhone or iPad — that's 4 days with no activation. I used the Terminal workaround on macOS 27 Golden Gate Beta (EnhancedSiriWaitlist → Enabled = NO), which successfully activated New Siri on my Mac. However, it has not synced to my other devices despite being on the same Apple ID with iCloud Siri sync enabled. Device details: Mac mini (macOS 27 Golden Gate Beta) — New Siri active ✓ iPhone (iOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 iPad (iPadOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 Steps already attempted: Multiple restarts on iPhone and iPad Toggled iCloud Siri sync off/on Toggled Siri off/on multiple times iCloud storage sufficient (200GB plan, 53GB used) 4 days seems far beyond normal rollout time. Is this a known issue? Is there anything on the account side that could be blocking activation? Thank you.
Replies
0
Boosts
0
Views
459
Activity
Jun ’26
DockKit for horse tracking
I am using a insta360 flow pro with iOS 18 public beta. What I would really like to see is tracking for horses .. is this a future implementation? Kind regards Chielio I would be happy to beta test this if it's in development.
Replies
0
Boosts
1
Views
543
Activity
Jul ’24
New Siri AI Stuck
I’ve tried every online recommendation but nothing works, someone helps me out , my WiFi is pretty good, 100GB storage space and I have left the phone plugged in for 5 consecutive days
Replies
0
Boosts
0
Views
706
Activity
Sep ’26
What is the correct way to modify a SceneStorage variable from an AppIntent to one scene only for iPad SplitView mode
Apple's sample code 'Trails' supports multiple scenes, however everything is using shared state across the scenes. Put the app in Split View mode and have two windows of the app running and navigate, you can see both mirror each other. Works as designed, it is using a shared 'navigation model' across all scenes. https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents I would like to know if there is a supported or recommended way to modify individual scene storage from within the perform body of an AppIntent. The objective is to have App Shortcuts that launch different tabs in a TabView or different selections in a List. In short, I want to deep link to features, but account for more than one scene being open on iPad and only have programatic navigation happen on the scene that is 'foremost' or the 'activated' one in Split View. I have it working with either a @Dependency or posting a Notification with my main ContentView listening to the other end, but it changes all scenes.
Replies
0
Boosts
0
Views
737
Activity
Aug ’24
Siri AI’s onscreen awareness can’t understand an AppEntity without a schema?
Use Case I’m currently developing , a hiking and cycling app. I’d like to use Siri AI in iOS/watchOS 27 to create an experience like this: While users are recording an activity in app, they can raise their wrist or invoke Siri on iPhone and simply ask: “How much farther to the destination?” “How far have I already gone?” “How much elevation gain is left?” “How far is it to the next waypoint?” … Siri can then answer based on the app’s current workout context. Since there are many metrics like these, and it’s not convenient to look at the screen while cycling or trail running, this could be a really valuable use case if Siri AI can support it. I defined an AppEntity like this, and then associated it with the UI. But I found that Siri AI doesn’t seem to understand this AppEntity. It can only understand the content it can see on the screen, even though I can see that it did execute ToobooWorkoutSessionQuery, the EntityQuery. This screen has multiple tabs. Siri understood the on-screen values such as “Distance: 0.21 mi” and “Remaining Distance: 0.14 mi”, but it didn’t know the data from the other tabs on the same page, such as heart rate, average speed, and so on. So it seems that Siri is directly reading the screen, instead of retrieving the information from the AppEntity I actually provided. Is this because the AppEntity doesn’t use one of the schemas defined by AppSchemaEntity, so Siri AI can’t understand it? App Intents without a schema seem to have a similar issue. If the AppIntent I define is not within one of those schemas, Siri won’t directly execute it either. My current solution: I defined many Intents and Shortcuts. Siri AI’s ability to parse shortcuts seems to be much smarter in the new system, and it can match them quite easily. Also, shortcuts don’t require the app to be in the foreground. However, when talking to Siri, the shortcut phrase has to include the app name, which feels a bit unnatural. For example: “How far have I traveled in xxx app?”
Replies
0
Boosts
1
Views
602
Activity
Jul ’26
Dependency between AssistantSchema.CameraEnum
Hi, I have some questions about the new AssistantSchema.CameraEnum.captureMode and AssistantSchema.CameraEnum.captureDevice introduced with iOS 18 beta 4. Here's the context. I create a intent: @AssistantIntent(schema: .camera.startCapture) struct StartCaptureIntent { var captureMode: CaptureMode var timerDuration: CaptureDuration? var device: CaptureDevice? func perform() async throws -> some IntentResult { .result() } } And these app enums: @AssistantEnum(schema: .camera.captureDevice) enum CaptureDevice: String { case front case back case ultrawide } @AssistantEnum(schema: .camera.captureMode) enum CaptureMode: String { case modeA case modeB } Some CaptureDevice cases are not available in some CaptureMode. e.g: CaptureMode.modeA only supports CaptureDevice.back and CaptureDevice.front. In a classic AppIntent, I would create an AppEntity to represent CaptureDevice and use @IntentParameterDependency<CapturePhotoIntent>( \.$captureMode) to create a dependency between the captureMode and the captureDevice parameters. How can we create this dependency between two @AssistantEnum? I'm not sure this is possible as @AssistantEnum creates AppEnum.
Replies
0
Boosts
1
Views
621
Activity
Jul ’24
Apple intelligence feature in macOS 15.1 beta software testing not working with compatible hardware and system settings
I am attempting to install the macOS 15.1 update alongside the Apple Intelligence beta feature, to experience and then integrate into my developing application. I have a compatible MacBook Air M2 with a regional designation of the United States and language as US English, but is however purchased in mainland China. i have downloaded 15.1 but apple intelligence does not display, is this arising from buying it in China?
Replies
0
Boosts
0
Views
839
Activity
Aug ’24
Some items are not functioning on iOS18.1 beta devices
I am checking actual movement on iOS18.1 beta 3 devices, but the following items are not functioning. Image Playground Image Wand Genmoji Please let me know the following Are the above 3 items available on iOS18.1 beta 3? If available, are there any other operations other than enabling Apple Intelligece that are required to use the features?
Replies
0
Boosts
0
Views
534
Activity
Sep ’24
Is it possible to set writingToolsBehavior globally?
Hello, we're investigating an option to disable writing tools for some customers in our app. I'm aware of the writingToolsBehavior property for UITextView etc, but we would like to have a way to set this globally without having to update all UITextView instances (or future instances). Is there any API to do this? We tried using UITextView.appearance.writingToolsBehavior = .none and it seemed promising on 18.2 beta, however it introduced crashes on devices running 18.1. The crashes look like: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Have you sent -setWritingToolsBehavior: to <UITextView: 0x14462c000; frame = (0 0; 0 0); text = ''; userInteractionEnabled = NO; gestureRecognizers = <NSArray: 0x30067cb40>; backgroundColor = UIExtendedGrayColorSpace 0 0; layer = <CALayer: 0x3009b1ba0>; contentOffset: {0, 0}; contentSize: {0, 0}; adjustedContentInset: {0, 0, 0, 0}> off the main thread? To verify, look for a complaint in the logs: "Unsupported use of UIKit…", and fix the problem if you find it. If your use is main-thread only please file a radar on UIKit, and attach this log. exercisedImplementations = { "setWritingToolsBehavior:" = ( ); }' Similarly, even on 18.2 beta if we used UITextField.appearance.writingToolsBehavior = .none we would see crashes for any search fields like: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Have you sent -setWritingToolsBehavior: to <UISearchBarTextField: 0x141c04a00; frame = (0 0; 0 0); text = ''; opaque = NO; gestureRecognizers = <NSArray: 0x301fe15c0>; placeholder = Search Leads; borderStyle = RoundedRect; background = <_UITextFieldSystemBackgroundProvider: 0x3015de960: backgroundView=<_UISearchBarSearchFieldBackgroundView: 0x141c60200; frame = (0 0; 0 0); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x3015de8e0>>, fillColor=(null), textfield=<UISearchBarTextField: 0x141c04a00>>; layer = <CALayer: 0x3015de240>> off the main thread? To verify, look for a complaint in the logs: "Unsupported use of UIKit…", and fix the problem if you find it. If your use is main-thread only please file a radar on UIKit, and attach this log. exercisedImplementations = { "setWritingToolsBehavior:" = ( ); }' Is it possible to set this globally?
Replies
0
Boosts
3
Views
499
Activity
Nov ’24
How to test for VisualIntelligence available on device?
I'm adding Visual Intelligence support to my app, and now want to add a Tip using TipKit to guide users to this feature from within my app. I want to add a Rule to my Tip which will only show this Tip on devices where Visual Intelligence is supported (ex. not iPhone 14 Pro Max). What is the best way for me to determine availability to set this TipKit rule? Here's the documentation I'm following for Visual Intelligence: https://developer.apple.com/documentation/visualintelligence/integrating-your-app-with-visual-intelligence
Replies
0
Boosts
0
Views
953
Activity
Sep ’25
Writing tools options
Hi team, We have implemented a writing tool inside a WebView that allows users to type content in a textarea. When the "Show Writing Tools" button is clicked, an AI-powered editor opens. After clicking the "Rewrite" button, the AI modifies the text. However, when clicking the "Replace" button, the rewritten text does not update the original textarea. Kindly check and help me showButton.addTarget(self, action: #selector(showWritingTools(_:)), for: .touchUpInside) @available(iOS 18.2, *) optional func showWritingTools(_ sender: Any) Note: same cases working in TextView pfa
Replies
0
Boosts
0
Views
479
Activity
Mar ’25
just curious
hey just curious if apple intelligence will be available on iPhone 15 Plus as well??? in october or is there a way that iPhone 15 Plus owners can join apple intelligence’s wait lists or something??? please let me know !😫
Replies
0
Boosts
0
Views
319
Activity
Sep ’24
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1 I am seeing a reproducible issue in Apple Mail on macOS 27 Developer Beta 1 where the compose body becomes locked/uneditable after using Apple Intelligence writing tools. Environment Mac: macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q Device: MacBook Pro with Apple Silicon shouldSwitchToCampoMode: false (isEnhancedSiriAvailable=false) App: Apple Mail Compose window Apple Intelligence Writing Tools Summary When composing an email in Apple Mail, if I write some text and then use Apple Intelligence to rewrite it — for example using Friendly, Professional, or Concise — Mail replaces the original text with the rewritten version. After the rewritten text is inserted, the message body becomes unresponsive. I cannot continue typing, edit the rewritten text, delete text, select text normally, or add new content inside the email body. The Apple Intelligence button also becomes unresponsive after this happens. The only actions that still seem to work are sending the email, discarding the draft, or using some toolbar actions such as emoji insertion. Steps to Reproduce Open Apple Mail on macOS 27 Developer Beta 1. Create a new email. Type any text into the email body. Use Apple Intelligence Writing Tools. Choose a rewrite option such as: Friendly Professional Concise Let Apple Intelligence replace/update the email body text. Try to click back into the message body and continue typing or editing. Expected Result After Apple Intelligence rewrites the email body, the compose field should remain fully editable. The user should be able to: Continue typing after the rewritten text Edit or delete the rewritten text Select and modify text Use Apple Intelligence again on the updated content Continue composing the email normally Actual Result After Apple Intelligence inserts the rewritten text: The email body becomes uneditable. Typing no longer works inside the message body. Clicking inside the body does not restore normal editing. Existing text cannot be edited or changed. Apple Intelligence controls become unresponsive. The compose window itself does not fully crash, but the body editor appears stuck. Send and discard still appear to work. Reproducibility This appears to be reproducible after using Apple Intelligence rewriting tools inside Apple Mail’s compose window. It was working before, so this appears to be a regression in macOS 27 Developer Beta 1.
Replies
0
Boosts
0
Views
269
Activity
Jun ’26
ToolIntent experience on watchOS
ToolIntent is currently marked unavailable on watchOS. (FB25455121) When Siri is invoked on Watch, what behavior(s) can users expect when invoking ToolIntents declared in our paired iOS codebase? Example use case: At their gym, a user leaves their iPhone face down nearby. To Siri on their Watch, they say "I just did 350 lbs 8 reps to failure" or "Rest for 3 minutes" or "Hack squat machine is busy, let's jump to the next exercise". If it matters, we benefit from extended background runtime via a mirrored live HKWorkout between our watch app and iPhone app (which displays a Live Activity).
Replies
0
Boosts
0
Views
267
Activity
1w