Skip to content

Google Play Console Notice: Direct links don't work #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ctechdev opened this issue Nov 28, 2023 · 3 comments
Open

Google Play Console Notice: Direct links don't work #426

ctechdev opened this issue Nov 28, 2023 · 3 comments

Comments

@ctechdev
Copy link

Bug Report

What happened?

In our production app we received warnings regarding incorrect handling of direct links, domain (host), and pathPatterns within intent-filter.
We are notified that:

  • Domain failed validation
  • Direct links don't work
    Users won't be taken directly to your app from links associated with this path, but they will see the app switcher or be taken to the web browser. Once you fix these issues and release a new version, users will need to update the app for the links to work."
    And the advice is this:
    " tag failed Add "/" to the beginning of the android:path attribute in the tag. The attribute can also be android:pathPrefix or android:pathPattern."
    We have replicated the same patterns as the testApp and so far we have not had any problems, how should we modify them to be valid?

currently it's like this:

<data android:host="*" />
<data android:pathPattern=".*\\.EPUB" />

Thanks in advance.

@uongsyphuong
Copy link

Has anyone solved this issue?

@stevenzeck
Copy link
Contributor

I'm not sure this is a toolkit problem. What are you trying to do exactly? I imagine domain validation fails because of the wildcard * in android:host.

@mickael-menu
Copy link
Member

Yes, it's not directly in the toolkit but in the test app. But I think it should still be mentioned in the documentation for anyone looking to implement side loading. I encountered the same Google Play warnings but couldn't find a solution. In practice though, it didn't cause any issues in the apps.

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

No branches or pull requests

4 participants