Skip to content

bug: play console reports the www.bitkit.to deep link as not working #1362

Description

@ovitrif

Refs:

What happened?

Play Console flags Bitkit's only verified web link as not working: "One deep link may be failing because your web domains aren't associated with your app" (Deep links page, 2.5.0 build 190: www.bitkit.to "Domain ownership not verified, Assetlinks JSON file failed to validate").

The manifest declares an android:autoVerify="true" App Link for https://www.bitkit.to/treasure-hunt (app/src/main/AndroidManifest.xml, the "Universal Links" intent filter on MainActivity). Two things are wrong with it:

  • https://www.bitkit.to/.well-known/assetlinks.json still names the old app, to.synonym.bitkit.wallet, so verification of to.bitkit fails. The file is served by nginx from the server, not from the website repository; synonymdev/synonym-website#245 tracks that fix.
  • Nothing in the app handles /treasure-hunt. The treasure hunt was never ported to Bitkit 2.x, feat: implement treasure hunt deeplink handling (app-side) #1079 was closed as not planned, and marketing confirmed no link uses it. Once the domain verifies, tapping such a link would open Bitkit and fail in the scanner.

Expected behavior

Play Console reports no failing deep links. The manifest claims only www.bitkit.to paths the app handles, and the domain verifies for to.bitkit.

Steps to Reproduce

  1. Open Play Console → Grow users → Deep links for Bitkit.
  2. See www.bitkit.to under Domains with "1 issue found".

Logs / Screenshots / Recordings

curl https://www.bitkit.to/.well-known/assetlinks.json returns a statement for to.synonym.bitkit.wallet only.

Bitkit Version

2.5.0 (190)

Device / OS

Android; Play Console report.

Reproducibility

Always.

Additional context

The fix has two parts:

  • App: remove the /treasure-hunt App Link from the manifest, or replace it with paths the app handles.
  • Server: publish assetlinks.json for to.bitkit with the Play app signing SHA-256 (synonymdev/synonym-website#245).

The custom scheme rows marked "Failed app checks" on the same page are the NFC NDEF_DISCOVERED filter, which has no VIEW action or BROWSABLE category by design; the VIEW filter for the same schemes shows "Deep linked".

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions