Skip to content

Fix Google Play Console flagging the test app's deep links - #821

Draft
mickael-menu wants to merge 1 commit into
developfrom
fix-issue-426
Draft

mickael-menu wants to merge 1 commit into
developfrom
fix-issue-426

Conversation

@mickael-menu

Copy link
Copy Markdown
Member

The Play Console flagged the test app with "Direct links don't work" because the ImportActivity VIEW intent filters declared http/https schemes with a wildcard host, which deep link validation cannot verify.

These schemes (and BROWSABLE) are unnecessary for side-loading: apps and browsers hand files over via content:// URIs, and a shared URL still reaches the HTTP import path through the SEND text/plain filter. The VIEW filters are now restricted to the content and file schemes, the vestigial app scheme is dropped, the rationale is documented in the manifest, and the "Opening a publication" guide gains a short side-loading section pointing at the manifest as the reference pattern.

No library code changed — test app and docs only.

Fixes #426

🤖 Generated with Claude Code

The Play Console flagged the test app with "Direct links don't work"
because the ImportActivity VIEW intent filters declared http/https
schemes with a wildcard host, which deep link validation cannot verify.
These schemes (and BROWSABLE) are unnecessary for side-loading, since
apps and browsers hand files over via content:// URIs. Remove them
along with the vestigial app scheme, document the rationale in the
manifest, and add a side-loading section to the "Opening a publication"
guide.

Fixes #426

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Google Play Console Notice: Direct links don't work

1 participant