Skip to content

[Bug] Scheduled messages shift to next day when set at exact hour (xx:00)[Bug] UI corruption after enabling read receipts (text/layout broken) #2130

@kisameayu

Description

@kisameayu

Title: [Bug] Scheduled messages shift to next day at exact hour & UI corruption after enabling read receipts (iOS)

Summary

Two critical issues introduced in recent Telegram updates are affecting core messaging functionality:

  1. Scheduled messages incorrectly shift to the next day when set at exact hours
  2. UI corruption occurs after enabling read receipts

Both issues are reproducible and significantly impact usability.


Issue 1: Scheduled Message Date Shift

Description:
When scheduling a message at an exact hour (e.g., 20:00), the system automatically shifts the scheduled date to the next day.

Example:

  • User selects: "Today at 20:00"
  • Actual result: Automatically changed to "Tomorrow at 20:00"

Key Condition:

  • Happens consistently when minutes are set to 00
  • Does NOT occur when minutes are non-zero (e.g., 20:01 works correctly)

Impact:

  • Breaks scheduling accuracy
  • Makes the feature unreliable for time-sensitive communication

Issue 2: Read Receipt UI Corruption

Description:
After enabling the read receipt feature, parts of the UI become visually corrupted.

Observed Behavior:

  • Text rendering appears garbled or misaligned
  • Layout is partially broken
  • Interface readability is affected

Impact:

  • Degrades user experience
  • Makes message status unclear

Environment

  • Platform: iOS
  • iOS version: 18.7.8
  • Telegram version: Latest (App Store)

Expected Behavior

  • Scheduled messages should remain on the selected date and time
  • UI should render correctly after enabling read receipts

Actual Behavior

  • Scheduled messages shift to the next day when set at exact hour (xx:00)
  • UI becomes corrupted after enabling read receipts

Notes

These issues appeared after recent updates and are not isolated edge cases.
They directly affect core messaging features and should be prioritized.

Screenshots can be provided upon request.


Request

Please investigate and confirm if these are known issues.
Any update on a potential fix timeline would be appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions