Thank you for your feedback. We have identified the cause and are working on a fix.

This feature has been fixed in version 2.0.3. The update has already been released, but it may take up to two days to become available on your device.