Add Cashtab dev builds to assetlinks.json

[Fabcien]

For this one only the debug key is supported. Since Cashtab uses flavored builds the app id is different for debug builds. Only the debug cert fingerprint is supported for this id.

Summary by CodeRabbit

• Chores
  • Updated app linking configuration to support URL routing for the development app version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 419f9fc and 0d31633.

📒 Files selected for processing (1)

• public/.well-known/assetlinks.json

---

📝 Walkthrough

Walkthrough

Adds a new Digital Asset Link entry for the development variant of the Cashtab Android app (com.cashtab.app.dev) to the assetlinks.json configuration file, enabling Android App Links support for the development app package.

Changes

Cohort / File(s)	Summary
Android Digital Asset Link Configuration public/.well-known/assetlinks.json	Added new assetlinks entry for com.cashtab.app.dev with delegate_permission/common.handle_all_urls relation and corresponding SHA256 certificate fingerprints.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Add Cashtab to the assetlinks.json #1112: Adds complementary com.cashtab.app entry to the same assetlinks.json file for the production Cashtab app.
• Update assetlinks.json #1107: Updates Android app fingerprint entries in public/.well-known/assetlinks.json for asset link configuration.
• feat: assetlinks json #1104: Modifies the same assetlinks.json file to add Android Digital Asset Links entries.

Suggested labels

enhancement (behind the scenes)

Suggested reviewers

• Klakurka
• chedieck

Poem

🐰 A dev app blooms in the asset links,
Where fingerprints dance and verification winks,
From .well-known depths, the rabbit did weave,
A path for the app—oh, how it can breathe!
Small change, big doors—the magic complete! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is incomplete. It lacks the required structure from the template including 'Related to #' issue reference and 'Test plan' section, though it does provide relevant context about debug key and flavor builds.	Complete the description by adding the related issue number and documenting the test plan for verifying the assetlinks configuration works correctly.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding Cashtab dev builds to assetlinks.json, which matches the file modification and PR objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}