Awesome, thanks. So everyone reporting this issue is on iOS. This narrows down our work to find a solution. Pls give us a couple days. I bet we can figure out a workaround.