Hello, an update for my side regarding this issue. It was driving me mad, I have tried everything I could think of but nothing worked. I have now gone back to v5.3.24 and disabled auto-update of the app. I have not encountered the issue so far, although may be it’s too early to conclude it certainly looks like it is related to a change in v5.3.27.
Hope this helps you to identify what it could be and provide a fix in a next version. If there’s any more info I can provide to help please let me know.
Regards,
Wouter
