This issue has been reported to development. It will be resolved on an upcoming update, tentatively scheduled for tomorrows (1/24) update.
View solution in original post
