Apple FaceTime url scheme does not initiate a call

By using Apple URL URL Link for FaceTime Links on a website, the link opens the FaceTime app, but does not pass the number / email to call or initiate a FaceTime call.

<a href="facetime:user@example.com">Connect using FaceTime</a>

      

Is this scheme supported? Any thoughts?

Additional info Edit: This is the actual code I'm using:

<a href="facetime:user@abc.com">Apple FaceTime</a>

      

This image displays a popup asking if I want to place a FaceTime call after clicking a link:

FaceTime call from webpage URL

This image shows an open FaceTime application with nothing happening.

FaceTime call from webpage URL

0


source to share


3 answers


Essentially, wait for the error to be fixed. When I responded to your comment on my post, and for the sake of another: Yes. This is a bug with iOS. I have reported this to Apple and they are currently fixed with the latest iOS beta. They just need to pull this fix out.



0


source


When you click on the facetime url from the webpage, it asks the user for permission. Automatic call initiation will only work from native applications and will not work with web pages.

From FacetimeLinks Reference



When a user clicks a FaceTime link on a webpage, iOS confirms that the user really wants to initiate a FaceTime call before proceeding. When an app opens a facetime URL, iOS opens the FaceTime app and initiates a call without prompting the user. When opening a FaceTime URL on OS X, the system always prompts the user before initiating a call.

+3


source


worth noting that this is an iOS 8 issue in Safari. We're struggling a bit with a web app that we developed on iOS 7.

This morning I thought I'd try Chrome on iOS 8 just to test it and it worked great. The link clicked, asked me to confirm that I wanted a FaceTime number, and launched and called the number as expected.

We still need to get this to work on Safari, but thought it might help focus on where the problem is occurring as I have treated this as a Facetime bug so far and it seems like a Safari bug.

Hope this is helpful,

Stewart

+1


source







All Articles