Ahh, this is a known issue! It should be fixed in the next update (coming soon!).