The original bug was that the WebOTP effect had [subView, triggerVerifyOtp] as its dependency array. triggerVerifyOtp is a useCallback that depends on [fetchProfile, onClose] - both of which can change reference during normal re-renders. Each reference change caused React to re-run the effect, which called AbortController.abort() on the still-pending OTP Promise. The user would see the 'Allow' modal, click Allow, but the Promise was already aborted so nothing happened. Fix: use triggerVerifyOtpRef (a stable ref) so the WebOTP effect only depends on [subView] / [step]. The ref is kept up-to-date via a dedicated sync effect. Additional improvements: - 400ms delay before auto-verify so user can see the filled boxes - toEnglishDigits on otp.code to handle Persian numerals in the response - Same fix applied to LoginModal (handleVerifyOtpWithCode -> verifyOtpRef)
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.