We have been battling this since Day 1. After working with Jamf a few times on this my only solutions are to
1 - repush the app
and if that alone does not work
2 - completely remove the device from the process by deleting it from the Profile - uninstalling the app - then adding it back
I have several devices that I have had to do this multiple times
So far the new version seems to be working as expected. I still have a few that stopped checking in before summer and now trying to work through those. A few just took a restart. One I had to uninstall Protect, remove from config, add back to config, redeploy pkg for it to check in again. Will see how it behaves going forward.
I am finding that any devices that have not restarted in over 30 days seem to stop updating the Protect version. Informing the staff to restart pulls the update. Guess it time to find one of those nifty scripts to prompt staff to restart every 30 days.