Hi all,
I develop and support a classroom management extension for schools. This provides teachers a realtime connection to student chromebooks during classtime.
We have been tracking an issue where from the teacher end, the student machine is acting as if the chromebook is closed (the runtime has not been terminated, but our code has stopped executing). We've been fortunate that some teachers have been able to chat in to troubleshoot while students are co-located in the same classroom, but even so we have reached the limitations of our ability to reason about the situation.
From what we know, there would be three reasons why the runtime would be paused:
1. The machine is not running
2. The extension is paused in developer tools
3. The student is currently taking a locked quiz in Google Classroom
It's easy for us to work through 1 and 2 with teachers. Additionally, most schools have had to disable developer tools for various reasons (different sites will embed the "correct answer" of a quiz in the source code, etc) through GSuite.
We've not found any way to verify that the machine has engaged Google Classroom (3). It's a very popular tool in classrooms, but it's not obvious if there are particular urls that we could have the teachers check or if there are any diagnostic pages we could have the teacher attempt to check that would show that this mode was engaged.
The other gap is that we have a handful of teachers who are claiming that the student's active window is on another domain than classroom when in this scenario. This implies there would have to be another scenario available, but again we've run out of tools for troubleshooting.
To be clear, our extension is using the background permission, so it is typically persistent. This is a very rare report from what I can tell. It's not a matter of the extension not being force-installed. It's not a matter of the extension being disabled. It's not a matter of the backing process of the extension being terminated. All the above go through the startup process in our extension. We have diagnostic logging we use to troubleshoot, and the breadcrumbs we leave behind look like it does when you pause the extension in dev tools.
Interested if anyone has any future insight on how to troubleshoot this kind of issue.
Thanks,
Joel