I just came across this same issue while attempting to install an eSDK.

 

So if AUTOREV can cause this behavior, is it possible to determine you're bitbaking an SDK/eSDK and alter AUTOREV into what the latest, for example, git hash is? That way, when installing the SDK, it'll just reference those static hashes at the time the SDK was built and this can be avoided?