New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767527 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Long OOO (go/where-is-mgiuca)
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 587623



Sign in to add a comment

navigator.getInstalledRelatedApps returns empty array

Reported by ybo...@oath.com, Sep 21 2017

Issue description

Chrome Version       : version 60.0.3112.116 on Google Pixel phone with Android version 7.1.2
URLs (if applicable) :


What steps will reproduce the problem?
(1) signed up for getInstalledRelatedApps origin Trial
(2) Updated the web to include meta tag with the token
(3) Updated the web to include "related_applications" in web manifest json file and included the manifest file on web.
(4) Updated android app AndroidManifest.xml with "asset_statements" to include the domain(abc.xyz.yahoo.com) which is sub domain of yahoo.com
(5) installed android app
(6) launch the web in the chrome and inspect in the browser.
(7) execute the following command in the browser console
navigator.getInstalledRelatedApps().then(relatedApps => {
  console.log(relatedApps);
});

What is the expected result?

it should print the package id of the installed app.


What happens instead?

Promise {[[PromiseStatus]]: "pending", [[PromiseValue]]: undefined}
[]

 
Labels: OS-Android

Comment 2 by mgiuca@chromium.org, Sep 22 2017

Cc: -mgiuca@chromium.org
Components: -Blink UI>Browser>WebAppInstalls
Labels: Needs-Feedback
Owner: mgiuca@chromium.org
It's hard to diagnose the problem without looking at the exact files involved (both the web and Android manifests).

Note the Digital Asset Links documentation:
https://developers.google.com/digital-asset-links/v1/statements

"A website target can only be a root domain; you cannot limit to a specific subdirectory; all directories under this root will match. Subdomains should not be considered to match: that is, if the statement file is hosted on www.example.com, then www.puppies.example.com should not be considered a match."

Android manifest must point to the exact domain that the web app code is served from. That could be the problem.

Comment 3 by ybo...@oath.com, Sep 22 2017

we were using the manifest.json file hosted on different domain from the page domain. that's why it was not working. We fixed the domain and it works now.

thank you for quick reply. 
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 22 2017

Cc: mgiuca@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mgiuca@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by mgiuca@chromium.org, Sep 25 2017

Status: WontFix (was: Unconfirmed)
Great to hear!

Sign in to add a comment