Some posters have mentioned that clearing the app cache fixed the problem for them. The dev has also pushed two updates to try and resolve the issue. Let us know if you’re still seeing it on v1.0.417.