Resuming email verification after the app is closed — the pending_email state that prevents re-sending
Background On first launch, the desktop app asks the user for an email address, sends a confirmation email, and completes registration once the user clicks the link in that email. There was a trap here for anyone who closed the app before clicking the link. Email does not always arrive immediately. Closing the app with the intention of clicking the link once the email shows up, then reopening…
Resuming email verification after closing the app presents two traps: re-entering the email address and an invalid link error. The desktop app initially asks for an email address, sends a confirmation email, and marks registration complete upon clicking the link in the email. However, if the user closes the app before clicking the link, the app defaults to the first-launch screen upon restart.
This results in re-entering the email address, which generates a new verification token and invalidates the first email link. To address this issue, the app now saves the sent email address to a local configuration file as pending_email upon successful email send. When the app restarts, it checks for pending_email and resumes the waiting screen if found.
The app does not call the server's registration endpoint during this resumption process, ensuring the first email link remains valid. Once verification completes, pending_email is cleared, and the registered flag is set. This small change prevents the trap of invalid links and simplifies the user experience by eliminating the need to re-enter the email address.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.
