Skip to content

fix: publish /invite/* in AASA + serve assetlinks.json under .well-known/ #304

@dcadenas

Description

@dcadenas

Part of divinevideo/divine-mobile#3697.

Two related fixes — same repo, same deploy.

1. Add /invite/* to the iOS AASA

File: public/.well-known/apple-app-site-association

Append to applinks.details[0].components:

{ "/": "/invite/*", "comment": "Invite redemption deep links" }

Without this, iOS won't hand /invite/{code} to the app even when the app declares applinks:divine.video (which it already does in Runner.entitlements).

2. Fix assetlinks.json 404 at .well-known/

Currently:

  • https://divine.video/.well-known/assetlinks.json → 404
  • https://divine.video/apple-app-site-association → 200 (served at root, not .well-known)

iOS tolerates either path; Android requires .well-known/assetlinks.json. The file exists in public/.well-known/assetlinks.json and _headers declares the Content-Type, but the live URL is not serving it. Investigate the Fastly Compute publisher's path-routing for .well-known/* and make it actually serve.

Acceptance

  • curl -s https://divine.video/.well-known/apple-app-site-association returns 200 JSON containing /invite/*.
  • curl -s https://divine.video/.well-known/assetlinks.json returns 200 JSON with the existing app cert fingerprints.
  • Apple's AASA validator and Google's Digital Asset Links validator both pass for divine.video.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Task.

    Projects

    Status

    In progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions