@jamesog so someone with the same issue just tried again shortly after and it worked. So could have been a temporary App Store server hiccup. Glad it’s resolved!