New issue
Advanced search Search tips

Issue 878711 link

Starred by 4 users
Status: Assigned
Owner:
poromov@chromium.org
Cc:
atwilson@chromium.org
msnoxell@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Kiosk mode hosted app are losing local state

Reported by pas...@lindelauf.com, Aug 29 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
Platform: 10718.71.2 (Official Build) stable-channel veyron_mickey

Steps to reproduce the problem:
This is non-deterministic. After months of correctly running a kiosk app, the Chromebit all of a sudden loses its local state which causes the app to lose its registration data.

What is the expected behavior?
The local state is always available and after each restart the kiosk app can retrieve its registration data to continue normal service.

What went wrong?
Upon restart of the Chromebit, the kiosk app does not find its registration data in the local store anymore, hence the user is requested to register this device (again). Since this is used in a digital signage context, it is hard and inconvenient to go through this process again. 

Even after re-registration, "defective devices" seem to see new occurrences of this problem in a couple of days again. 

Note that these devices have worked correctly for multiple months, during which they were restarted daily. 

Did this work before? Yes Unsure

Chrome version: 68.0.3440.87  Channel: stable
OS Version: 68.0.3440.87
Flash Version: Google_Veyron_Mickey.6588.264.0

This report stems from this discussion: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/p9mDc8oaDtM
chromebit-_lost_registration_debug-logs_20180828-160155.tgz
1.6 MB Download

Comment 1 by poromov@chromium.org, Aug 29

Components: Enterprise

Comment 2 by rogerta@chromium.org, Aug 30

Labels: Enterprise-Triaged
Owner: atwilson@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by rogerta@chromium.org, Aug 30

Owner: shubhar@chromium.org

Comment 4 by atwilson@chromium.org, Aug 31

Cc: atwilson@chromium.org
Owner: poromov@chromium.org
+poromov can you have your team take a look at these logs and see if we can figure out why kiosk state is being lost?

Comment 5 by msnoxell@chromium.org, Sep 3

Cc: msnoxell@chromium.org

Comment 6 Deleted

Comment 7 by allanrobert@chromium.org, Sep 5 

Do you have any update on this issue?
We have another important Japanese Enterprise customer (>300 devices) that is experiencing the same problem but it is on kiosk chromebook (ninja) 

After rebooting, the login screen pops up, when the identification is done the application starts up automatically but it is reset to zero and the initial activation code to start the app is requested as if it was used for the first time. 

Unify #16795300
Chrome/Platform Version 
68.0.3440.118 
10718.88.2 (Official Build) stable-channel ninja 
Firmware Version 
Google_Ninja.5216.383.7
►

Sign in to add a comment