When I create a definition and a patch policy and it keeps returning unknown version how do I fix that. The Mac is in a patch loop at this point. Do I need sudo jamf recon or a new extension attribute?
So, just to be clear, you have a patch definition and corresponding patch policy set up for an application that the Jamf Pro server does not recognize (yet) and it keeps downgrading the application? I assume also that this application is getting upgraded later to the new version, only to be downgraded again by Jamf. Are those all correct assumptions?
Or, is this more about how you get your JSS to recognize the new version? If so, there isn't anything you can do directly about that. Jamf has to update their definitions for the new releases, which they usually do within a small number of days after it's out.
If it's the first scenario, I recommend unchecking both the "Allow Downgrade" and "Patch Unknown Versions" options in the patch policy settings, as shown. Or maybe just one of them to start.
If you have either or both of those enabled, its likely downgrading the product and, maybe it's something like Google Chrome where it keeps updating itself later, so it keeps coming up as an unknown version.
Hopefully that helps? If I'm off the mark on what the issue is you're experiencing, maybe you can explain a little further.
I'm using CommunityPatch.com for my defs on Slack.app . The user says they keep getting prompted to quit the app for the update. Slack is already on the newest version, but Jamf see's it as Unknown. So he's in a patch looping trying to install what has already been installed. I only have the Patch Unknown Versions turned on. I have other Macs that are working fine. I didn't know if something was broke with the version info so a extension attribute could fix or not.
@kericson whose definition of Slack are you using from CommunityPatch?
All except one are reporting 3.3.3 still (contributor Fishd has theirs updated to 3.3.7). Assuming you're subscribed to one of the feeds with 3.3.3 and you have Patch Unknown Versions turned on what's going to happen is users that have updated to 3.3.7 are going to get downgraded to 3.3.3 since that's the latest version for your patch policy.