Posted on 06-16-2019 09:19 PM
Currently on
JAMF Pro 10.4.0
&
JAMF Pro 10.8.0
&
JAMF Pro 10.10.0
All our JSS's have an issue with what appears to be a Google Chrome issue.
Whenever we edit or create a policy and add/remove packages, we either get erratic behavior. Adding packages to policies don't add and end in a spinning circle forever (see attached).
We narrowed it down to this version of Google Chrome on both Mac and Windows.
Version 75.0.3770.90
Logging.html returns a strange issue (see attached)
Solved! Go to Solution.
Posted on 07-30-2019 05:01 PM
Dear All,
This issue according to JAMF Pro's 10.14.0 release notes has been resolved.
JAMF Pro 10.14.0 Release Notes
[PI-007099] Fixed an issue that prevented administrators from saving or canceling a policy when adding scripts or packages to the policy and using Google Chrome version 75.0.3770.80.
Posted on 06-16-2019 09:50 PM
Oh! And I thought it was just me. I haven't got around to clearing the browser cache to see if that fixes the issue, as I have too much open...
Posted on 06-16-2019 11:00 PM
This should be more easy to find, but here is the links...
PI-007099 When using Google Chrome release 75.0.3770.80, adding scripts or packages to policies prevents you from saving or cancelling the policy. Workaround: Use a different browser.
Posted on 06-17-2019 05:22 AM
I've also had this! I only use Chrome for work so this is really annoying.
I guess it'll also affect the current dev preview of Edge on Mac (which is excellent if anyone is wondering) as it's basically the same browser.
Posted on 06-23-2019 09:48 PM
Also seeing this on Chrome 75.0.3770.100.
Confirming the original post, looking through the JSS log you see some really strange errors
2019-06-24 14:39:08,873 [ERROR] [Thread-5 ] [HTMLController ] - Exception processing HTMLResponse:
java.lang.NullPointerException
at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source)
at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source)
at java.lang.String.compareToIgnoreCase(Unknown Source)
at com.jamfsoftware.jss.objects.policy.PolicyHelper$10.compare(PolicyHelper.java:1536)
at com.jamfsoftware.jss.objects.policy.PolicyHelper$10.compare(PolicyHelper.java:1533)
at java.util.TimSort.countRunAndMakeAscending(Unknown Source)
at java.util.TimSort.sort(Unknown Source)
at java.util.Arrays.sort(Unknown Source)
at java.util.ArrayList.sort(Unknown Source)
at java.util.Collections.sort(Unknown Source)
Is there a planned fix for this ? Has it been logged to Google Chrome devs, or is it an issue on the JSS side of things - anyone know ?
Posted on 06-24-2019 01:26 AM
Seeing this as well. Works fine in Edge (MS Edge, not Chromium Edge) but it's really laggy in comparison.
Posted on 07-11-2019 02:53 AM
Chrome (Version 75.0.3770.100) has the same behaviour on macOS (with JAMF Pro 10.12). Really annoying, Safari works as a workaround.
I hope it will get fixed soon.
Posted on 07-18-2019 06:53 AM
Still a thing with Chrome version 75.0.3770.142 (Official Build) (64-bit). Issue reproduced after clearing caches and in Incognito mode. Issue reproduced on first install, not signed in to Chrome sync and with no extensions.
Safari works.
Posted on 07-27-2019 10:15 AM
<expletive><expletive><expletive>!!!
Wish I'd seen this yesterday afternoon...at least now I know what's going on with the policy I'm trying to create.
Posted on 07-30-2019 07:09 AM
This applies to all Chromium browsers as well (IE Brave). Still exists with all latest versions. Very frustrating.
Posted on 07-30-2019 07:11 AM
Seeing this also. Have to switch to Firefox if I want to make policy changes.
Posted on 07-30-2019 07:42 AM
Edge Chromium as well (but obviously it's now Chromium based so not surprising).
Posted on 07-30-2019 05:01 PM
Dear All,
This issue according to JAMF Pro's 10.14.0 release notes has been resolved.
JAMF Pro 10.14.0 Release Notes
[PI-007099] Fixed an issue that prevented administrators from saving or canceling a policy when adding scripts or packages to the policy and using Google Chrome version 75.0.3770.80.