Good catch! This issue will be resolved with a future update. Thanks!