Hey All,
I suspect you're running into this issue:
There are some workarounds available, but I don't think the firmware team has had a chance to look into this yet, but hopefully soon!
Thanks! David