Login and authentication issues

Symptom: you click the magic link in your email and land on the login page instead of the app.

Cause: the most common cause is email security software (Microsoft Defender, Proofpoint, corporate antivirus gateways) that pre-fetches links in incoming emails before you click them. This invalidates the one-time token in the link before you can use it.

Fix: use the 6-digit OTP code from the same email instead of clicking the link. The code cannot be pre-fetched by security software. Enter your email on the login page, click Continue, then enter the code in the OTP field.

Symptom: clicking the magic link from the iOS Mail app opens a page but does not log you in, or the session does not persist when switching to Safari.

Cause: the Mail app on iOS opens links in its own in-app browser, which is isolated from Safari and does not share session storage. This is a privacy design choice by Apple and affects all web apps using email-based authentication.

Fix: use the 6-digit OTP code. Copy the code from the email, open Numwisely in Safari (not from the Mail link), enter your email, tap Continue, then enter the code. This method works reliably on all iOS devices.

Symptom: clicking the magic link shows a "token has expired or is invalid" error message.

Cause: links expire after 60 minutes, or the link was consumed by email security software.

Fix: return to the login page and request a new magic link. If the same error repeats, switch to the OTP code method.

Symptom: you requested a magic link but no email arrived.

Fix steps: (1) Check your spam or junk folder. (2) Confirm the email address you entered is correct — typos are common. (3) Wait 2–3 minutes — delivery can be delayed during high-traffic periods. (4) Try requesting a new link. (5) If you use a company email domain, ask your IT team to whitelist the sender address.

Symptom: you were logged in, restarted the browser, and now need to log in again.

Cause: browser settings cleared cookies or local storage on close. This is a browser privacy setting, not an app issue.

Fix: check your browser settings for "clear cookies on close" or similar privacy options. Disable this setting for the Numwisely domain if you want your session to persist.