New issue
Advanced search Search tips

Issue 919517 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Today
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Provisioning flow was interrupted while installing Google Play Store

Reported by mfors...@partnerswi.com, Jan 7

Issue description

Chrome Version: 71.0.3578.94
Chrome OS Version: 11151.59.0
Chrome OS Platform: Acer ALY03781U10N Spin 11 R751t-c4xp 11.6
Network info: Wifi, EAP/PEAP, Ruckus

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Enable ARC is enabled in Active Directory Group Policy
(2) User logs into Chromebook and Google Play Store starts to install
(3) Login screen for Identity Provider displays
(4) After username and password is filled out Google Play Store resumes installing
(5) Installation stops with the message "Provisioning flow was interrupted. Please try again or contact your device owner or administrator". Subsequent attempts have the same result.

Expected Result: Plays Store installs without issue.

Actual Result: Play Store does not get installed

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?) 

Always

What is the impact to the user, and is there a workaround? If so, what is
it? 

There is no workaround as one of our software vendors keeps mission critical apps in the Play Store

Please provide any additional information below. Attach a screen shot or
log if possible. 

The play Store installs and works in Chrome OS version 66.0.3359.158 and prior.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Components: Platform>Apps>ARC

Comment 2 by elramos@google.com, Jan 16 (6 days ago)

Can you run the command for network diagnostic and confirm if the issue isn't caused by a ssl restriction? 

Check the following help center for further information
https://support.google.com/chrome/a/answer/3504943?hl=en&ref_topic=3504941

Comment 3 by elramos@google.com, Jan 16 (6 days ago)

Cc: elramos@google.com

Comment 4 by mfors...@partnerswi.com, Jan 17 (5 days ago)

Ran network_diag --hosts and all tests passed.

Thanks,
Mike

Comment 5 by weifangsun@chromium.org, Jan 18 (4 days ago)

Components: Enterprise

Comment 6 by ryutas@google.com, Jan 21 (2 days ago)

Cc: ryutas@chromium.org
Labels: -Pri-3 Hotlist-Enterprise Pri-2
We’ve received additional info regarding this case.

Case#: 18044599

• TIMEFRAME WHEN ISSUE STARTED • 
Few days ago, from the moment the ticket was created. 

• DOES IT AFFECT ALL DEVICES • 
Only one device reported so far. 

• TROUBLESHOOTING STEPS TAKEN • 
1. I wiped the device. This did not change the situation. 
2. I wiped the device and reverted back to the original version of Chrome OS that came with it (66.0.3359.158). This allowed me to install the Play Store, but this only lasted until the device updated itself to 71.0.3578.94. The issue started again and all of the apps that were installed became unusable. 
3. I deprovisioned the device, wiped it, and logged in with a regular gmail account without adding the device to our domain. I was able to install the Play Store. This is not a work around as we need the devices joined to our Active Directory domain so they can be managed through Group Policy. 
4. Whitelisted Google’s URLs 
5. Admin Console > Device Management > Chrome Management > Android Application Settings > Enable Android applications for your domain, the "Enable Android applications to be managed through the Admin Console" was checked when I visited the page a couple of days ago and this morning when I looked at that setting again. 
6. I powerwashed the Chromebook, logged in before joining the domain, changed it's channel to beta, powerwashed it again, and then joined it to the domain. The issue remains. 
7. I edited that GP, verified that the Chromebook downloaded and applied it, but there is no change in behavior. Yesterday I did switch from beta to dev and that cleared up the problem. I signed into my idp and Play Store, as well as the apps listed in the Configure ARC GP, installed without issue. I switched back to stable this morning after I configured the EcryptfsMigrationStrategy GP to Migrate Automatically and the issue reappeared. 

• EXISTING WORKAROUND • 
Switching from Beta to Dev 

Android Application Settings Screenshot: https://drive.google.com/open?id=1yHnwUayWaJ9X_Orz36g2HUe4olQnPNf4
About Version: https://drive.google.com/open?id=11jCN2reLC1K5x3o_DeGylYPMcLRHSubO
Debug Logs: https://drive.google.com/open?id=1JPHFs8_TdMyuAbugPUu3Ftv6Tr4lcMZ-
Policies New: https://drive.google.com/open?id=11vqh3uUgUup-0N1IetRRotHw9NDhgmWP
Policies Old:https://drive.google.com/open?id=14zmLDlNJ0TTwk5dODYBJBm2tAiz8Ul91
ARC and Kernel message:https://drive.google.com/open?id=19-gGxDNeCQu4UYsw7mkvlg7Mhwkj5c_kRv90oBvbpRM

Comment 7 by chchakrapani@google.com, Today (6 hours ago)

Status: Closed (was: Unconfirmed)
Google Play store installed and able to search/install/launch arc applications.(eg: temple run)

Closing the bug, as the reported scenario is not reproducible.

Additional Information:
"Android Device policy" can't be installed due to Error code:910

Attached logs and screenshots.


debug-logs_20190122-150839.tgz
1.7 MB Download
policies.json
24.7 KB View Download
Screenshot 2019-01-22 at 15.08.29.png
365 KB View Download
Screenshot 2019-01-22 at 15.07.36.png
167 KB View Download
Screenshot 2019-01-22 at 15.06.43.png
156 KB View Download

Sign in to add a comment