ionic-team / capacitor-docs

https://capacitorjs.com/docs
Apache License 2.0
20 stars 193 forks source link

'Deep Links' doc may need to be updated for new Apple deeplinks API? #193

Open xml opened 1 year ago

xml commented 1 year ago

URL https://capacitorjs.com/docs/guides/deep-links#create-site-association-file

What is missing or inaccurate about the content on this page? First, thank you for Capacitor and for great docs! I make this suggestion uncertainly, so please accept in that spirit.

In the apple site association file, the doc uses the syntax for details of associating to each appID a paths property which contains URL's. And, I can find this syntax in an archived document from the Apple Developer Library.

Ex.

{
  "applinks": {
    "details": [
      {
        "appID": "TEAMID.BUNDLEID",
        "paths": ["*"]
      }
  ]

But in what seems to be the latest and greatest docs from Apple, they use a whole different syntax for details, which associates components instead of paths. Components are pattern matchers that seem to logically serve as an alternate to a simple path, but more flexibly and powerfully.

Ex.

{
  "applinks": {
      "details": [
           {
             "appIDs": [ "ABCDE12345.com.example.app", "ABCDE12345.com.example.app2" ],
             "components": [
               {
                  "#": "no_universal_links",
                  "exclude": true,
                  "comment": "Matches any URL with a fragment that equals no_universal_links and instructs the system not to open it as a universal link."
               }
            ]

Source(s):

In all of those documents, I see the component syntax consistently repeated, and no evidence that a paths syntax is operative, at least not in recent versions of iOS.

Again, I am totally new to this topic, and am learning it by working through your excellent guide, so it's entirely possible I'm missing something. But... when I use the paths syntax with iOS 14... I can't get it to work. So, I checked the Apple docs, and found what seems like a mis-match in the API... Please share feedback about whether this is a valid point or noob confusion. Thanks!

Fillsen commented 1 month ago

agree