I am experiencing the same. Has anyone found a resolution.

Xxxxxxxxxxxxxxxx ~ % sudo jamf recon -verbose      

 verbose: Timeout: 10

 verbose: Checking availability of xxxxxxx/…

 verbose: JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword

 verbose: Error Domain=com.jamf.jamfsecurity.error Code=-25293 "unlockWithPassword:error: : The user name or passphrase you entered is not correct." UserInfo={NSLocalizedDescription=unlockWithPassword:error: : The user name or passphrase you entered is not correct.}

There was an error.

     Device Signature Error - A valid device signature is required to perform the action.

I'm seeing this as well on machines. 

sudo jamf enroll -prompt 

and re-enrolling seems to fix.

I had a stubborn MacBook Pro that wouldn't finish inventory. The "sudo jamf enroll -prompt" worked for me. Thanks!

Old thread I know, but recently had a bunch of machines failing to check in. What I found is that majority of these machines were running "jamf policy" and getting stuck, some of them went back months even.

I ran a "sudo killall jamf" on them, followed by "jamf policy" and they started checking in again without the need to re-enroll the device(s).

I do have a 3rd party patching tool though that allows me to push out scripts and stuff to machines, so that helped bypass Jamf where it couldn't talk to machines.

Its not ideal but better then walking around to 34-40 machines. I think Jamf should deploy some sort of failsafe where if a policy runs for so many hours or days it kills itself and restarts. I think that would fix a lot of these issues where machines are falling off and failing to check in.

Hope this help others.

Didn't fix the issue for me, still hangs on "Locating hardware information".
Macos 12.6.9
Jamf 10.50.0