Actually, I think I just managed to replicate the issue, the JWT key name is case sensitive, so if you have it set as PID in your JWT and pid in Tyk as the policy source then the error you describe appears (because Tyk can’t find the key in the JWT claims, it can;t locate the policy).
On a different note, running theough your scenario with the correctly cased claim names has the versioning work just fine 