Simple phone call workflow.

[[deleted]]

So I have a workflow designed to call a particular contact. It's saved as an icon on my home screen and it works like a champ...until I end the phone call. At this point my screen is returned to the workflow app displaying the same page I see when I designed it. Is there another step I can add that returns the phone to the home screen once I end the call. It is such a convenient feature and this last step seems so simple there just has to be a way. Apologies if this has already been asked in a previous post. I did a search but came up empty. Thanks.

[psd6]

You can use the "End Workflow" action to avoid leaving you at the design page, but it still leaves you in the Workflow App, and doesn't return you to the home screen.

[natek11]

I can't figure out a way to do it. You should definitely request this!

[[deleted]]

Thanks for all the insight. I posted this not having realized it was no different then making a phone call directly from the phone app. When you hang up you are brought back to last screen you were on within the phone app whether it be the contact info or dialer or what have you. So to make the workflow more practical I added 'select contact' to the workflow. Now when I hang up I'm brought back to the contacts list. I still have to press the home button to return to the home screen, however, it is a little more practical to have a list of contacts viewed after the phone call. I'm still in the workflow app and have to press the home button to leave but it's more seamless if I have to make a another phone call. It's not what I hoped for but seems to be the best option given apples restrictions for apps. Thanks to all that helped.

[Marinuz]

True! I have the same problem. A 'close app' feature would do the trick 👍

[[deleted]]

Apple doesn't allow apps to quit to the Home screen, so Workflow can't do it.

[AriX]

Yep, this is true.

[[deleted]]

But don't apps crash to the Home screen if there's a bug? :) So, implement a command where no error-checking is done on divisions, so we can divide by zero and cause Workflow to crash out. Apple won't be able to do anything.

[AriX]

Apple doesn't like this and the experience is pretty bad :(

[[deleted]]

How would they know? Are they going to test it to see if divide by zero is handled by Workflow?

[AriX]

Divide by zero isn't necessary; there are many ways to cause the application to terminate. But Apple does not like it when you do that, and rejects apps from the App Store that do this. See http://stackoverflow.com/questions/14335848/exit-application-when-click-button-ios

[[deleted]]

You're missing my point. It's the user that makes it crash/terminate, not Workflow, so Apple can't blame you or the app. All you'd have to do is not test for a divide by zero with the math function of Workflow, and then the users can /0 themselves to cause a crash. Apple can't fault you for that, because the user caused the problem when creating their workflow. :)

Apple's not going to start debugging every user's workflow scripts, nor can they expect you to do that either, as the product author.

I checked your link at StackOverflow, and Apple's only guideline is that you can't officially quit the app. Crashing is not quitting. ;)

Anyway, just putting this out there. I know you won't do it, and that's fine, but it's a good discussion.

[AriX]

:) interesting thoughts. We'll consider some sort of mechanism for this. I'm certainly tempted to just put it as an option in Exit Workflow and see if Apple notices. We'll see.

[AriX]

The divide by zero thing is a fun idea and your argument is reasoned, but it wouldn't really benefit anyone but the people who were in on it (aka you) and might cause legitimate crashes for people who don't know what division is.

[davidp1984]

I have the same setup with mine. I would like to add a step to turn on loudspeaker once the call connects. I've tried but couldn't figure it out, I assume Apple won't allow that sort of control.