Interesting... TBH I didn't run into that issue, so I'm not sure what is the best way to get around it. However, just by looking at the error, creating a link seems to be the only solution on top of my mind since it looks like this particular build included a more detailed version (a build number maybe?). Please let me know if there is a solution other than creating a link that I missed.