Problem statement
The phone verification flow stores data.token in localStorage after resending an OTP, but this repo does not appear to read that value anywhere anymore.
This looks like leftover logic from an older flow and makes the current behavior harder to reason about.
In src/views/PhoneRegistration.tsx:
- resend phone OTP
- parse response JSON
- if
data.token exists, write it to localStorage
There does not appear to be any active consumer of that stored token in this package.
Proposed solution
Acceptance criteria
- No stale or unexplained
localStorage writes remain in the OTP flow
- Tests reflect the intended behavior
- If token storage remains, it has a documented purpose and an active consumer
Alternatives considered
No response
Problem statement
The phone verification flow stores
data.tokeninlocalStorageafter resending an OTP, but this repo does not appear to read that value anywhere anymore.This looks like leftover logic from an older flow and makes the current behavior harder to reason about.
In
src/views/PhoneRegistration.tsx:data.tokenexists, write it tolocalStorageThere does not appear to be any active consumer of that stored token in this package.
Proposed solution
Acceptance criteria
localStoragewrites remain in the OTP flowAlternatives considered
No response