What happens if apple-app-site-association paths overlap

What will happen if a users opens https://example.com/profile/123 and apple-app-site-association looks like this:


{
    "applinks": {
        "apps": [],
        "details": {
            "9JA89QQLNQ.com.app.one": {
                "paths": [
                    "/profile/*"
                ]
            }
            "9JA89QQLNQ.com.app.two": {
                "paths": [
                    "/profile/*"
                ]
            }
        }
    }
}


My guess is that this behavior is undefined, but I haven't had a chance to setup an experiment to see what actually happens. Has anyone tried this?


It would be really nice if details were an array and not a dictionary so that there would be an implicit priority (i.e. the first app that is installed and whose path matches will handle the the universal link).

I have a similar problem with universal app links. I have a series of related apps that reuse URLs on the same domain, and I have set up my .json file accordingly.


Oddly enough, it is working for one of my apps but not getting caught in the others. I couldn't find any documentation on what kind of patterns we are allowed to use there, and it's possible that matching on pieces of a path is not currently possible (I have URLs of the form of /m/xx* that go to one app, and /m/yy* that go to another), or maybe it's just not working properly.


Something is happening on my app though, as the links open the app directly without going to Safari, and they are passed properly. It's just that they all go to the same app instead of the appropriate one if the pattern matching was in effect.

What happens if apple-app-site-association paths overlap
 
 
Q