Spent a futile few hours today trying to figure out why Casper Admin 9.65 was crashing when trying to upload a new .pkg or .dmg to it. Went down a lot of rabbit holes before finally contacting JAMF Tech Support, who told me that there's an open defect with packages and .dmgs that have "com.apple.x.x" in their names.
Turns out that it looks like it might be something with any .pkg or .dmg with multiple periods in its name. As soon as I renamed my .pkg and .dmg to have only a single period, Casper Admin stopped crashing.
Hope this helps someone else.
I've had Casper Admin crash a lot just after finishing uploading/copying a PKG. Opened a case, then troubleshot by nuking all JAMF prefs from my ~/Library/Preferences folder (and doing a killall cfprefsd). Lo and behold, the crashes stopped. Something you might want to try, since it did legitimately help me...
Just to be clear, I'm only guessing about the common denominator being that "com.apple.x.x." files and my software "AdwareAlert.app.pkg" having multiple periods as being the culprit. It's an educated guess, but it might also be that both had "app" in them somewhere. Again, only guessing. What I know is that renaming my installer package "AdwareAlert.pkg" allowed it to be uploaded without crashing Casper Admin. YMMV.
P.S. The project I was working on is a modified version of CocoaDialog that lets me throw up an alert message with clickable URLs and a mailto: link. Once I have my "AdwareAlert.app" distributed to all my managed machines, I can easily have a script open it if a machine falls into the "AdwareDetected" smart group.
Interesting, I'm trying to upload a script to Casper Admin and its crashing each time I try. I guess I'll play with the name to see if its maybe too long.
Princeton Public Schools