Can't call INPauseWorkoutIntent without home button
up vote
0
down vote
favorite
I have implemented INPauseWorkoutIntent, INStartWorkoutIntent or INResumeWorkoutIntent in my app in IOS 12 and XCode 10. I can use the commands correctly with using home button to open Siri but what I need is Hand off. I mean, I just want to say "Pause workout" and it should pause. I also don't want to use watch. How to achieve that, what am I missing?
Note: - (id)handlerForIntent:(INIntent *)intent not called anyways.
ios siri sirikit
edited Nov 8 at 20:14
rmaddy
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
add a comment |
up vote
0
down vote
favorite
I have implemented INPauseWorkoutIntent, INStartWorkoutIntent or INResumeWorkoutIntent in my app in IOS 12 and XCode 10. I can use the commands correctly with using home button to open Siri but what I need is Hand off. I mean, I just want to say "Pause workout" and it should pause. I also don't want to use watch. How to achieve that, what am I missing?
Note: - (id)handlerForIntent:(INIntent *)intent not called anyways.
ios siri sirikit
edited Nov 8 at 20:14
rmaddy
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have implemented INPauseWorkoutIntent, INStartWorkoutIntent or INResumeWorkoutIntent in my app in IOS 12 and XCode 10. I can use the commands correctly with using home button to open Siri but what I need is Hand off. I mean, I just want to say "Pause workout" and it should pause. I also don't want to use watch. How to achieve that, what am I missing?
Note: - (id)handlerForIntent:(INIntent *)intent not called anyways.
ios siri sirikit
edited Nov 8 at 20:14
rmaddy
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
I have implemented INPauseWorkoutIntent, INStartWorkoutIntent or INResumeWorkoutIntent in my app in IOS 12 and XCode 10. I can use the commands correctly with using home button to open Siri but what I need is Hand off. I mean, I just want to say "Pause workout" and it should pause. I also don't want to use watch. How to achieve that, what am I missing?
Note: - (id)handlerForIntent:(INIntent *)intent not called anyways.
ios siri sirikit
ios siri sirikit
edited Nov 8 at 20:14
rmaddy
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
edited Nov 8 at 20:14
rmaddy
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
edited Nov 8 at 20:14
rmaddy
235k27305371
edited Nov 8 at 20:14
rmaddy
235k27305371
edited Nov 8 at 20:14
rmaddy
235k27305371
235k27305371
asked Nov 8 at 19:15
birdcage
1,17322039
asked Nov 8 at 19:15
birdcage
1,17322039
asked Nov 8 at 19:15
birdcage
1,17322039
1,17322039
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I believe you already have implemented resolve, confirm, and handler functions comforting to respective protocols.
I just check response code for workout and they have .continueInApp response code.
That being said, I believe you can pass response with code .continueInApp and save whatever parameters you have to use in UserActivity in handler's completion. UserAcitivity will be passed to application: continueUserActivity function in AppDelegate; so you can pause it from there.
If handlerForIntent is not called, then I believe intent is not understood by Siri
answered Nov 8 at 19:51
Hikaru Watanabe
12211
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I believe you already have implemented resolve, confirm, and handler functions comforting to respective protocols.
I just check response code for workout and they have .continueInApp response code.
That being said, I believe you can pass response with code .continueInApp and save whatever parameters you have to use in UserActivity in handler's completion. UserAcitivity will be passed to application: continueUserActivity function in AppDelegate; so you can pause it from there.
If handlerForIntent is not called, then I believe intent is not understood by Siri
answered Nov 8 at 19:51
Hikaru Watanabe
12211
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
add a comment |
up vote
0
down vote
I believe you already have implemented resolve, confirm, and handler functions comforting to respective protocols.
I just check response code for workout and they have .continueInApp response code.
That being said, I believe you can pass response with code .continueInApp and save whatever parameters you have to use in UserActivity in handler's completion. UserAcitivity will be passed to application: continueUserActivity function in AppDelegate; so you can pause it from there.
If handlerForIntent is not called, then I believe intent is not understood by Siri
answered Nov 8 at 19:51
Hikaru Watanabe
12211
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
add a comment |
up vote
0
down vote
up vote
0
down vote
I believe you already have implemented resolve, confirm, and handler functions comforting to respective protocols.
I just check response code for workout and they have .continueInApp response code.
That being said, I believe you can pass response with code .continueInApp and save whatever parameters you have to use in UserActivity in handler's completion. UserAcitivity will be passed to application: continueUserActivity function in AppDelegate; so you can pause it from there.
If handlerForIntent is not called, then I believe intent is not understood by Siri
answered Nov 8 at 19:51
Hikaru Watanabe
12211
I believe you already have implemented resolve, confirm, and handler functions comforting to respective protocols.
I just check response code for workout and they have .continueInApp response code.
That being said, I believe you can pass response with code .continueInApp and save whatever parameters you have to use in UserActivity in handler's completion. UserAcitivity will be passed to application: continueUserActivity function in AppDelegate; so you can pause it from there.
If handlerForIntent is not called, then I believe intent is not understood by Siri
answered Nov 8 at 19:51
Hikaru Watanabe
12211
answered Nov 8 at 19:51
Hikaru Watanabe
12211
answered Nov 8 at 19:51
Hikaru Watanabe
12211
answered Nov 8 at 19:51
Hikaru Watanabe
12211
12211
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
add a comment |
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
handlerForIntent is not called at all. what might be the reason why its not called?
– birdcage
Nov 8 at 19:54
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
In Info.plist, did you define which Intents are used in IntentExtension's plist? You have to define all the Intent you use in plist's NSExtension.developer.apple.com/documentation/sirikit/…
– Hikaru Watanabe
Nov 8 at 19:56
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53214664%2fcant-call-inpauseworkoutintent-without-home-button%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
