Department.io hosted AASA file is invalid for iOS 12 units

[ad_1]

I not too long ago seen that customers on iOS 12 weren’t in a position to observe our Department hyperlinks (firm.app.hyperlink) to our app. Upon additional investigation I discovered this error within the iOS 12 system logs:

### Obtain URL 'https://firm.app.hyperlink/.well-known/apple-app-site-association' failed: -6756/0xFFFFE59C kTypeErr 

After researching error -6756/0xFFFFE59C it appears that evidently the AASA file mechanically hosted and generated by Department just isn’t utilizing an accurate a schema for iOS 12 units:

{
  "applinks": {
    "apps": [],
    "particulars": [
      {
        "appIDs": ["ABC123.com.company.app", "ABC123.com.company.app"],
        "parts": [
          {
            "/": "*",
            "?": {
              "$web_only": "true"
            },
            "exclude": true,
            "comment": "Matches any URL whose path is * and which has a query item with name '$web_only' and value 'true' and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "*",
            "?": {
              "%24web_only": "true"
            },
            "exclude": true,
            "comment": "Matches any URL whose path is * and which has a query item with name '%24web_only' and value 'true' and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "/e/*",
            "exclude": true,
            "comment": "Matches any URL whose path is /e/* and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "*",
            "comment": "Matches any URL whose path is * and instructs the system to open it as a Universal link"
          },
          {
            "/": "/",
            "comment": "Matches any URL whose path is / and instructs the system to open it as a Universal link"
          }
        ]
      }
    ]
  }
}

I have been in contact with Department assist and have offered a repair that I’ve verified to work with iOS 12 and newer iOS variations – however sadly they have not been very useful. I do not assume that is associated to a foul configuration as I can affirm that the difficulty impacts different excessive profile Department.io prospects.

The repair I discovered was to mix the previous and new AASA codecs right into a single file (by including the appId and path keys again into the file). I’ve examined this on iOS 12, 15 and 16 units and might affirm that the domains are appropriately related to our app and that deep linking works as anticipated (however I am undecided how technically appropriate this resolution is):

{
  "applinks": {
    "apps": [],
    "particulars": [
      {
        "appIDs": ["ABC123.com.company.app", "ABC123.com.company.app"],
        "appID": "ABC123.com.firm.app",
        "parts": [
          {
            "/": "*",
            "?": {
              "$web_only": "true"
            },
            "exclude": true,
            "comment": "Matches any URL whose path is * and which has a query item with name '$web_only' and value 'true' and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "*",
            "?": {
              "%24web_only": "true"
            },
            "exclude": true,
            "comment": "Matches any URL whose path is * and which has a query item with name '%24web_only' and value 'true' and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "/e/*",
            "exclude": true,
            "comment": "Matches any URL whose path is /e/* and instructs the system NOT to open it as a Universal link"
          },
          {
            "/": "*",
            "comment": "Matches any URL whose path is * and instructs the system to open it as a Universal link"
          },
          {
            "/": "/",
            "comment": "Matches any URL whose path is / and instructs the system to open it as a Universal link"
          }
        ],
        "paths": ["*"]
      }
    ]
  }
}

Can anybody shed some extra gentle on this concern or maybe touch upon the validity of mixing the previous and new AASA codecs into one? Or maybe level me in the proper route – I could not discover a lot data on supporting related domains on each iOS 12 and newer iOS variations on the identical time.

[ad_2]

Leave a Reply