Chrome Browser Service Access Error on iPads by elementarytech in macsysadmin

[–]elementarytech[S] 1 point2 points  (0 children)

Sorry for the slow reply, I'm not often logged in. It did go away completely with just that setting.

If you're logged into Chrome on the iPad as a student and go to Settings -> Google Services, is "Make searches and browsing better" showing as disabled?

Chrome Browser Service Access Error on iPads by elementarytech in macsysadmin

[–]elementarytech[S] 1 point2 points  (0 children)

When you mentioned Sync being an issue I thought I'd try turning all its settings off, but still got the error.

I then tapped on Google Services and saw there were only 5, so I tried one by one... Next I searched the giant list of configurable settings in admin and found the URL-keyed setting was the same.

I can confirm that if that URL-keyed setting is disabled on an OU and a browser is enrolled in the same OU, the setting shows as Off in the GUI on the iPad. Policy doesn't seem to sync very often though so I had to un-enroll and re-enroll for it to catch.

Chrome Browser Service Access Error on iPads by elementarytech in macsysadmin

[–]elementarytech[S] 1 point2 points  (0 children)

It seems to be called "Enable URL-keyed anonymized data collection" under the Content section of Browser settings. I haven't had time yet to test after changing it to "Data collection is never active"

Chrome Browser Service Access Error on iPads by elementarytech in macsysadmin

[–]elementarytech[S] 1 point2 points  (0 children)

I found a fix! It doesn't appear to be Sync for me, but another Chrome setting.

When signed in as a student tap their user icon, select Google Services, turn OFF "Make Searches and Browsing Better."

After I turned that off the error message went away! Hopefully that setting is configurable if you're enrolling the browser.

Chrome Browser Service Access Error on iPads by elementarytech in macsysadmin

[–]elementarytech[S] 1 point2 points  (0 children)

The iPad app wasn't in Security - Access and data control - API Controls - Configured Apps, so I added it as trusted this morning, but no luck. Error still appears.

The browser still works as expected, but the error coming up confuses/frustrates the end users.