SFSafariViewController delegate callback for URL loading

Originator:an00na
Number:rdar://21511683 Date Originated:23-Jun-2015 04:44 PM
Status:Closed Resolved:
Product:iOS Product Version:iOS 9 beta 2
Classification:Feature (New) Reproducible:Not Applicable
 
The only thing that prevents me from using SFSafariViewController instead of my own UIWebView/WKWebView wrapper is the the lack of delegate callback for URL loading.

I understand that for protecting user’s privacy general sniffing is forbidden. However, prescribed and limited URL detection is non-intrusive and very useful for users. For example, if a Twitter app knows that user taps a link to a tweet it can present a native tweet view with better user experience.

So I suggest that developers are allowed to specify in app’s info.plist several URL domains that the app wants to process and SFSafariViewController send delegate calls when navigating to matching URLs.

Comments

Observation

The only callback technique appears to be using custom URI schemes, that is what was recommended in https://developer.apple.com/videos/wwdc/2015/?id=504 [ascii: http://asciiwwdc.com/2015/sessions/504]. Quote: "And once the user is finished logging in and the third-party web service redirects back to your app with the custom URL scheme that you fed it, you can accept that in your AppDelegate's handleOpenURL method."

By william.denniss at June 30, 2015, 8:51 p.m. (reply...)

Apple Developer Relations

There are no plans to address this.

We are now closing this report.

If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

By an00na at June 29, 2015, 11:19 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!