Hi. We apologize for the inconvenience. We have fixed the issue in version 4.22.1 of the app, which is rolling out to users gradually over the next 24 hours or so. When you are able, please update to the latest release (version 4.22.1) to fix the problem.