This has been fixed in today's update. Thank you so much for pointing this out. Can't believe I missed it
