Ios 9 Not Opening Instagram App With Url Scheme

iOS 9 not opening Instagram app with URL SCHEME

iOS 9 has made a small change to the handling of URL scheme. You must whitelist the url's that your app will call out to using the LSApplicationQueriesSchemes key in your Info.plist.

Please see post here: http://awkwardhare.com/post/121196006730/quick-take-on-ios-9-url-scheme-changes

The main conclusion is that:

If you call the “canOpenURL” method on a URL that is not in your whitelist, it will return “NO”, even if there is an app installed that has registered to handle this scheme. A “This app is not allowed to query for scheme xxx” syslog entry will appear.

If you call the “openURL” method on a URL that is not in your whitelist, it will fail silently. A “This app is not allowed to query for scheme xxx” syslog entry will appear.

The author also speculates that this is a bug with the OS and Apple will fix this in a subsequent release.

iOS9 - Sharing to Instagram (w/ hooks) not working

After changing this line of code:

NSURL *igImageHookFile = [[NSURL alloc] initFileURLWithPath:newJpgPath];

to this:

NSURL *igImageHookFile = [NSURL URLWithString:newJpgPath];  

The Instagram-share function for iOS 9 is now working. It seems that the previous line of code, converting the NSString to an NSURL would place "--://file" at the end of the URL path, which doesn't seem to register well with iOS 9. Simply converting the NSString to NSURL without initialising as a file URL seems to work.

Opening installed app using URL Scheme is not working

I don't see a problem on your side, seems like everything is set correctly.
However, regarding iOS 9, other users reported this problem with iframe. Make sure the things are setup correctly on server side. Check these 2 links:

iOS 9 iFrame Problem 1

iOS 9 iFrame Problem 2

iOS 9 safari iframe src with custom url scheme not working

The previous answer is a partial implementation of Universal Links that is missing critical details and doesn't include a fallback to the App Store.

First, you can no longer set iframe src in order to trigger a URI scheme. You've correctly identified that issue. As you noted, you can, however, still set window.location = 'custom-protocol://my-app';. So if you know that a user has your app because you've previously opened their app from the browser and have a cookie stored that can be looked up on your backend, you can still safely fire custom-protocol://.

Second, you can detect the user agent string using navigator.userAgent. Pre-iOS 9 you can still use the iframe to fire a URI scheme, then fallback after a timeout. On iOS 9, you can choose whether to fire the URI scheme or not based on cookies, then take the user to the App Store. I work on this at Branch and making use of cookies to recall whether a user likely has the app is something we've implemented. Feel free to reach out if you have more questions about that, or make use of our solution directly.

---

Implementing Universal Links is not quite as simple as the other answer describes. In reality, there is considerably more complexity. Here's a complete list of steps (I've helped several apps integrate in recent weeks using these steps):

1. Configure your app to register approved domains

i. Registered your app at developer.apple.com if you haven't

ii. Enable ‘Associated Domains’ on your app identifier on developer.apple.com

iii. Enable ‘Associated Domain’ on in your Xcode project

iv. Add the proper domain entitlement, applinks:yourdomain.com, in your app

2. Configure your website to host the ‘apple-app-site-association’ file

i. Buy a domain name or pick from your existing

ii. Acquire SSL certification for the domain name (you can use CloudFlare for this!)

iii. Create structured ‘apple-app-site-association’ JSON file

{
   "applinks": {
       "apps": [ ],
       "details": {
           "TEAM-IDENTIFIER.YOUR.BUNDLE.IDENTIFIER": {
               "paths": [
                   "*"
               ]
           }
       }
   }
}

iv. Sign the JSON file with the SSL certification

v. Configure the file server

The apple-app-site-association file:
- must be sent with the header ‘application/pkcs7-mime’
- must be sent from the endpoint youdomain.com/apple-app-site-association
- must return a 200 http code.

Example Express+Node:

var aasa = fs.readFileSync(__dirname + '/static/apple-app-site-association');
app.get('/apple-app-site-association', function(req, res, next) {
     res.set('Content-Type', 'application/pkcs7-mime');
     res.status(200).send(aasa);
});

credit: borrowed liberally from this blog post

---

Related Topics