Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] BlockBlock 2.5.2 displays alert timestamps in UTC instead of local time

Open
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
objective-c

Research direction

Start in Daemon/Daemon/Event.m and trace how ALERT_TIMESTAMP reaches the UI helper through the existing XPC path. Replace the string-based timestamp flow with a date value and format it for the logged-in user’s timezone and locale. Done means alerts display local, localized timestamps instead of UTC while retaining the correct date and time.

Written by the indexing model from the issue text.

Description

My Mac is set to America/Sao_Paulo (UTC−03), but BlockBlock 2.5.2 displays alert timestamps in UTC.

Actual: 2026-09-28 12:57:27 AM +00
Expected: 2026-09-27 9:57:27 PM -03

In Daemon/Daemon/Event.m, the timestamp is generated using NSDate.description:

alert[ALERT_TIMESTAMP] =
    (nil != self.file.timestamp.description)
    ? self.file.timestamp.description
    : self.timestamp.description;

The UI helper then displays this string directly:

self.timeStamp.stringValue = self.alert[ALERT_TIMESTAMP];

Could alert timestamps use the user’s local timezone? Ideally, the daemon would send the date over XPC, and the UI helper would format it using the logged-in user’s timezone and locale.

Thank you!

Dominant language
Objective-C
Stars
859
Forks
50
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from objective-see/BlockBlock

All issues in objective-see/BlockBlock

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.