Looks like HCL changed the fixlet not long after releasing it with revised SHA1 hashs. Our Prod just happened to not get it as quick as Dev, but Prod is seeing the revised fixlet now.
It’s working fine in our Dev environment, which is same BES version/config/etc… Will try again, maybe just a fluke.
Not sure if it’s just me, but getting SHA1 error on Chrome download. Never had this before on a Chrome fixlet deployment.
“Error processing completed download: Requested sha1 cd65cd58a17d10573f0dc39eaaa882c7a0689621 does not match actual sha1 149bb7ae817bf1d745b0b17f073b1eadb77bacf4”