For me this was also happening exactly as described (including the comment) but strangely enough the built version of the application no longer had this issue. You can try to run the built version locally to confirm if it's the same for you.