Yes this is a known issue with our iOS build only. We already fixed it; a patch will be out as soon as it passes App Store review.