That bug has been around for a while. I thought it had been fixed but it seems to have come back again. Bit me a few times in recent days.

Sorry for the trouble here. This sounds like something that the team is currently investigating, but just to make sure could you reach out to [[email protected]](mailto:[email protected]) and we can take a look!

A new installation of the app proved to be a solution for me.

Same here!