AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Verification code expiration time is not synced with user timezone, newest first.

Current version | Edited by Rex
Changes
Details[image](https://feedback.fluxer.com/p/312#f-298)Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Verification code expiration time is not synced with user timezone

Observed behaviour

The code is functional and can be used to verify the new mail adress. However, the email template displays a "stale" expiration time (e.g., 15:01 for an email received at 15:51). This is strictly a display/timezone conversion issue in the email notification, not a functional bug of the code generator. Expected behaviour The expiration time should reflect the user's local timezone (e.g., if received at 15:51, it should say "expires at 16:01" for a 10-minute window).

Reproduction steps

  1. Trigger an email change request.
  2. Receive the email (e.g., at 15:51 local time).
  3. Check the expiration time stated in the email body.

Details

Timezone Mismatch in Emails

I noticed a consistency issue with the verification timestamps.
  • Email received at: 15:51 (Local Time / CET)
  • Stated expiration time: 15:01 (Same day)
The verification code appears to be "expired by 50 minutes" the moment it is received. It seems the backend is using UTC/GMT for the expiration timestamp without converting it to the user's local timezone in the email template. The verification code itself works perfectly, but the expiration timestamp displayed in the email is confusing. The backend provides the time in UTC/GMT instead of the user's Local Time, making the code look like it expired 50 minutes ago even though it’s still valid.
Environment (optional)
  • Windows 11 Pro
  • Local Time: Paris/France (CET/UTC+1)
Logs or screenshots (optional)
image
Original by Rex
Show

Verification code expiration time is not synced with user timezone

Observed behaviour

The code is functional and can be used to verify the new mail adress. However, the email template displays a "stale" expiration time (e.g., 15:01 for an email received at 15:51). This is strictly a display/timezone conversion issue in the email notification, not a functional bug of the code generator. Expected behaviour The expiration time should reflect the user's local timezone (e.g., if received at 15:51, it should say "expires at 16:01" for a 10-minute window).

Reproduction steps

  1. Trigger an email change request.
  2. Receive the email (e.g., at 15:51 local time).
  3. Check the expiration time stated in the email body.

Details

Timezone Mismatch in Emails

I noticed a consistency issue with the verification timestamps.
  • Email received at: 15:51 (Local Time / CET)
  • Stated expiration time: 15:01 (Same day)
The verification code appears to be "expired by 50 minutes" the moment it is received. It seems the backend is using UTC/GMT for the expiration timestamp without converting it to the user's local timezone in the email template. The verification code itself works perfectly, but the expiration timestamp displayed in the email is confusing. The backend provides the time in UTC/GMT instead of the user's Local Time, making the code look like it expired 50 minutes ago even though it’s still valid.
Environment (optional)
  • Windows 11 Pro
  • Local Time: Paris/France (CET/UTC+1)
Logs or screenshots (optional)
image
Checks
  • ☑ I searched for existing issues and didn't find a duplicate.