Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events starting on the timestamp 0 aren't visible in the app #440

Open
7 tasks done
Aga-C opened this issue Jan 23, 2025 · 0 comments
Open
7 tasks done

Events starting on the timestamp 0 aren't visible in the app #440

Aga-C opened this issue Jan 23, 2025 · 0 comments
Labels
bug Something is not working niche Only relevant to a very small amount of people

Comments

@Aga-C
Copy link
Member

Aga-C commented Jan 23, 2025

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.1.0

Affected Android/Custom ROM version

Android 13

Affected device model

OnePlus 8 Pro

How did you install the app?

GitHub releases

Which calendar service or provider do you use, if any?

No response

Which sync adapter app do you use for calendar synchronization, if any?

No response

Steps to reproduce the bug

  1. Change timezone to GMT+00:00 Greenwich Mean Time.
  2. Create an event that starts on 1970-01-01 at 12 AM.

Expected behavior

The event should be visible in the app.

Actual behavior

The event isn't visible in the app, but is still saved in the database.

Screenshots/Screen recordings

No response

Additional information

This behavior isn't only in GMT+0. I can reproduce it also in GMT+01:00 Central European Standard Time, but with start time set to 1 AM.

What's worth noting, in GMT+0 it affects also all-day events (as they always get start_ts at the beginning of the day), so e.g. if someone wants to import an event like:

BEGIN:VEVENT
UID:nyd
SUMMARY:New Year's Day
DTSTAMP:20250122T223653Z
DTSTART;VALUE=DATE:19700101
DTEND;VALUE=DATE:19700102
STATUS:CONFIRMED
RRULE:FREQ=YEARLY
END:VEVENT

it won't be visible on any occurrence.

@Aga-C Aga-C added bug Something is not working niche Only relevant to a very small amount of people labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working niche Only relevant to a very small amount of people
Projects
None yet
Development

No branches or pull requests

1 participant