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

Issue 718131 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Get Help app: Android apps section seen on non-android devices

Project Member Reported by sdantul...@chromium.org, May 3 2017

Issue description

Google Chrome	59.0.3071.35 (Official Build) dev (64-bit)
Revision	0
Platform	9460.23.0 (Official Build) dev-channel link

What steps will reproduce the problem?
1. Open Get Help app on non android device
2. Check for Android apps section

What is the expected result?
Android apps section should not be present

What happens instead?
Android apps section is seen.

Attached screenshot
 
Screenshot 2017-05-03 at 12.13.53 PM.png
825 KB View Download
Owner: morsed@chromium.org
Status: Assigned (was: Untriaged)
morsed@ - Could you take a quick look to see if this is a regression?

Comment 2 Deleted

Comment 3 by morsed@google.com, May 5 2017

Status: Started (was: Assigned)
I am showing the same thing on Pixel/link device I have, Android apps topic is incorrectly appearing, even though the device is correctly providing the "not available" signal for playStore.


Google Chrome	59.0.3054.0 (Official Build) dev (64-bit)
Platform	9413.0.0 (Official Build) dev-channel link


Using the console to inspect the app:  (via chrome://inspect/#apps)

chrome.chromeosInfoPrivate.get(['playStoreStatus'], console.log)  
Object {playStoreStatus: "not available"}


Perhaps it's something with gKMS transition to Redwood.  The rule was originally written to be compatible with pre-ARC++ devices, and can be updated when M54 is no longer a relevant OS version.  I'll follow up with Casey and Tiffany.

I believe this is the rule in gKMS and Redwood for reference: 
https://gkms.corp.google.com/Client.html#7194464 
https://redwood.corp.google.com/7194464

Comment 4 by morsed@google.com, May 5 2017

The API call the Get Help app is making looks correct (for current/legacy API):

https://www.googleapis.com/support/v1/topics/3477855?key=AIzaSyCOx7NTvlw6XxqOj0Dm4dvebQguJ4z0frw&helpcenter=chromeos&hl=en_US&extra_param=source.genius&extra_param=deviceinfo.link&extra_param=playStore.not%20available&extra_param=managedDevice.managed&maxLevels=-1 

Looking at the extra_param "playStore.not%20available" perhaps it's an issue with capitalization??  The rule in Redwood identifies Signal name: URLParameter.playstore 

Comment 5 Deleted

Comment 6 by morsed@google.com, May 17 2017

A ticket has been opened to create a new parameter to try within the existing ARC++ rule:

http://b/38354411 

"add 'URLParameter.playStore' with a capital "S" as a valid signal in Redwood"

Comment 7 by morsed@google.com, May 31 2017

Status: Fixed (was: Started)
Signal updated to 'URLParameter.playStore' with a capital "S", as indicated in http://b/38354411.  Tested by morsed@ and caseymo@ on ARC++ and non-ARC++ devices. 
Labels: -Type-Bug Type-Bug-Regression
Status: Assigned (was: Fixed)
Issue is fixed on M60 (9592.22.0, 60.0.3112.34)

but regressed again on M61 TOT 9656.0.0, 61.0.3132.0 link, peppy
Cc: mkarkada@chromium.org sdantul...@chromium.org
 Issue 757640  has been merged into this issue.
From the duplicated bug above, issue is still reproducible on latest M61 9765.35.0 
Owner: caseymo@chromium.org
+caseymo@ - Hi Casey, do you have any thoughts on why this behavior might have regressed? Looks like it should have been fixed with the update in b/38354411?

Comment 13 by case...@google.com, Aug 23 2017

Owner: weifangsun@chromium.org
Sadly, I don't know. :/ That update should have fixed it. The Android apps folder (in Redwood) and its rules/parameters haven't been touched since this bug was fixed in May.

I've looped in Tiffany (our configs specialist) on b/38354411 to check the rule & see if anything has regressed, but unfortunately there's nothing I can do on my end yet. Assigning back to you for now.

Comment 14 by case...@google.com, Aug 23 2017

Cc: -weifangsun@chromium.org caseymo@chromium.org

Comment 15 by case...@google.com, Aug 23 2017

Cc: weifangsun@chromium.org
Labels: -M-59 M-61
Owner: xiaoyinh@chromium.org
Status: Fixed (was: Assigned)
This appears to be the same root cause as b/68362395, and should be fixed by 
https://chrome-internal-review.googlesource.com/c/chromeos/chromeos-assets/+/494672
Status: Verified (was: Fixed)
10092.0.0, 64.0.3256.0
Labels: -M-61 M-64

Sign in to add a comment