We have made an update here — this issue should be resolved.