@jim @vincent I was just looking at that and think I have it fixed for the next update this week. Already submitted to Apple.