Thanks for all these details. I believe this issue is fixed in the iOS build that we just released (3.0.28). Can you please upgrade and confirm?