Chrome application not detecting enrollment status about loaner HOT 17 CLOSED

from loaner.

Check the following:

1. In the APP_DOMAINS variable in constants.py, the primary GSuite domain should be listed first and any secondary domains listed after. If that is not the case, fix, redeploy, migrate traffic.

2. Double check the deployment files to ensure you are using the correct Client ID. The Chrome App ITEM ID from the Chrome Web Store App may be incorrectly placed where Chrome App OAUTH client ID should have been. The Chrome App ITEM ID should not be added to any of the deployment files. If that is the case, fix, redeploy, migrate traffic.

3. Check that the OAuth Consent Screen is set to "Public". GCP > API > Credentials > OAuth Consent Screen.

If all those look good, check the output from the following:

(On the Chromebook) Chrome://extensions ---> Dev Mode on > background page > Reproduce > Check Console Section in background.html / index.html
or
(On the Chromebook) Chrome://extensions ---> Dev Mode on > Details > Toggle on Error Reporting > Reproduce > Check Error Section

from loaner.

I have the same issue. Went through everything multiple times and now am having the "This device is not enrolled in the Grab N Go program. Please contact your administrator." error as well.

Device is enterprise enrolled and is in the Org > Grab n Go > Prod > Default OU

from loaner.

from loaner.

@templesnr yeah that's exactly what I have setup. I checked the BigQuery table and it's showing that the devices have been enrolled in to GnG.

It gives me the error instantly which is odd. It's like it's not even going outbound to check if it's actually enrolled.

from loaner.

Have you checked the debug view CTRL + SHIFT + 9? If so, please share a screenshot so we can attempt to troubleshoot further. Additionally, is there any logs in GCP for the heartbeat from this device?

from loaner.

I'm seeing NULL in the heartbeat column on BigQuery...

When I add a device through the GnG console > Devices it gets moved from the top level OU where I enterprise enrolled to the Grab and Go > Prod > Default OU so it's certainly communicating with Chrome Management.

from loaner.

I would recommend against using BigQuery for debugging issues such as these. StackDriver logging (Logging option on Google Cloud Platform) will provide fairly in-depth info about what is happening when requests are made. Additionally, any luck in grabbing a screenshot from the debug view (CTRL+SHIFT+9 on the Chromebook you're having issues with)?

from loaner.

Pardon my ignorance... Where am I launching debug mode? The application just fires off a notification when I launch it. I've enabled error logging on the extension and here's what I see.

And the notification:

Also FWIW here's the stack driver output. seems to be checking in every half-hour with no errors.

from loaner.

Do you see any heartbeat requests on StackDriver? It's possible you've misconfigured the loaner/shared/config.ts if there are no heartbeats making it to the backend. Additionally, which version of the application are you running? This one looks like it's out-of-date considering that the notification doesn't include a "DEBUG" button.

My recommendation would be to pull the latest version from HEAD (latest commit to the master branch). Once you do this, make sure all your configured values are properly set once again and then update the web app and Chrome App.

If you're still hitting this issue after updating, you can launch the debug view doing CTRL+SHIFT+9 from the Chrome OS device with the Grab and Go application installed.

from loaner.

@helfrichmichael Figured I'd let you know I got this working. I think my issue was more of a timing thing and wasn't being patient with things propagating on the chrome dev dashboard side.

from loaner.

Similar issue here. Some devices do not detect enrollment status. These devices are in the Default OU (ChromeOS -> Grab n Go -> Prod -> Default) and are enrolled in the program as well.
One thing I noticed is that they do not have a heartbeat (last_heartbeat is null). There are several devices that work just fine.
One thing to note here is - The version running is 0.7.1. I will be updating this to latest master to check.
Do we have any insight on what might be the issue?

from loaner.

Okay. So I went ahead and deployed the master version of the app. I think I have a handle on the error now. The Chrome app is requesting the URL https://chrome-dot-dev-app-engine-project.appspot.com and this is resulting in a null heartbeat.
I used bash to deploy the web app using deploy.sh for prod (deployments/deploy.sh web prod) and used bash deployments/deploy.sh chrome prod to deploy the chrome app.
Any pointers here?

from loaner.

@akshitbaunthy this means you haven't configured the shared/config.ts file.

Please see: https://github.com/google/loaner/blob/master/docs/setup_guide.md#sharedconfigts and https://github.com/google/loaner/blob/master/docs/deploy_chrome_app.md#step-3-keying-the-chrome-app specifically step #5.

This means that in your config.ts, you haven't defined your endpoints (it's pointing to the default dev instance). If you are expecting it to be pointing at PROD right now, that additionally means that you likely haven't configured the CHROME_PUBLIC_KEYS for each environment. This is how the application figures out which release track it is on.

As for deploying, I typically build the chrome app using NPM, zip up the directory, and upload it as a new version of the existing app to the Chrome Web Store.

from loaner.

@helfrichmichael - Thank you for your response.
I checked and you were right. The CHROME_PUBLIC_KEY was incorrect. I screwed up line breaks. Fixed it, compiled both the web and chrome apps. Awaiting propagation.
Just wondering though, is that the only thing that can cause this? Since the error actually points to chrome-dev and I haven't put in ANY details for any of the other instances.

from loaner.

Yup. Thanks a tonne, @helfrichmichael.

from loaner.

Great to hear @akshitbaunthy. I'll mark this as closed, but don't hesitate to let us know if you're having any further issues.

from loaner.