Project

General

Profile

Actions

Bug #1480

open

Session Expired Error Persists After OTP Resend on Verification Screen

Added by khadija tul Kubra 3 days ago. Updated 2 days ago.

Status:
New
Priority:
High
Target version:
-
Start date:
04/08/2026
Due date:
% Done:

0%

Estimated time:

Description

Description
On create account flow, after entering the OTP on the verification screen and waiting for the timer to expire, clicking the Continue button shows a “Session Expired” error. Even after resending the OTP and entering the new code within the valid time, the same error persists, preventing the user from proceeding.

Steps to Reproduce

  • Navigate to the Register/Create Account screen
  • Enter valid details and proceed to the Verification Code (OTP) screen
  • Enter OTP
  • Wait for the 1-minute timer to expire
  • Tap Continue → observe error
  • Tap Resend Code
  • Enter the new OTP within valid time
  • Tap Continue again

Actual Result

  • “Session Expired” error is shown
  • Error persists even after resending OTP
  • User cannot proceed further

Expected Result

  • After resending OTP:
  • A new valid session should be created
  • User should be able to proceed with the new OTP
  • “Session Expired” error should only appear for truly expired sessions

Files

Actions #1

Updated by Muhammad Shahid 2 days ago

  • Assignee changed from Muhammad Shahid to haroon sajjad
Actions #2

Updated by haroon sajjad 2 days ago

The issue is occurring because the application continues to use an invalid/previous session ID instead of the newly generated one. As a result, the system keeps returning a "session expired" message. The app is not updating or utilizing the latest session ID after it is regenerated, which leads to this behavior.

I have also attached a video demonstrating the behavior in different scenarios. It clearly shows what happens when an expired session ID is used, when a valid session ID is used with an incorrect OTP, and when both the session ID and OTP are correct. This should help clarify the responses returned by the system in each case.

Actions #4

Updated by haroon sajjad 2 days ago

  • Assignee changed from haroon sajjad to Muhammad Shahid
Actions

Also available in: Atom PDF