Yes, I’ve tried everything—clearing the app’s data and cache, uninstalling it, and reinstalling it. As I mentioned in my feedback about the 3.2 update, I exchanged several emails with Proton support, tested multiple alpha versions of the app as well, and we concluded that the problem lies with the /e/OS system.
I just posted the bug report on GitLab.