Skip to content

calendar appears empty #1386

Open
Open

Description

@JperiodMichael

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.11.0

Affected Android/Custom ROM version

Android 10

Affected device model

Moto G Play

How did you install the app?

Google Play Store

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

n/a

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

n/a

Steps to reproduce the bug

Opened app, my calendar was empty. Switched to "Simple Event List", still empty.
Flailed about, enabled Google Calendar app, tried restoring from .ics file (repeatedly), disabled Google Calendar app
gave up, manually added Event I had intended to modify, saved new event, suddenly entire calendar was populated, including Events created after the last .ics file was created.

Expected behavior

expected to see my calendar whenever I look at my calendar

Actual behavior

my calendar appeared to be empty

Screenshots/Screen recordings

No response

Additional information

It is the considered opinion of Google's A.I. that the problem resulted from me not looking at my calendar for long enough that Android severed the connection between the calendar app and its database, but that the calendar app did not work hard enough to test and restore the connection. And that the act of actually writing a new event was enough to cause the app to properly reestablish its connection to the database.

I was forced to lie and check the box that said I could reproduce the issue with the latest version. I did not download the latest version. I am unable to reproduce the bug, even with Google A.I. providing a never-ending stream of suggestions: tried setting the toggle in Developer Options for "Don't Keep Activities" -- didn't reproduce the problem; tried setting Background Process Limit to "No background processes" -- didn't reproduce it. Then it became Google A.I.'s opinion that what was needed was for me to go several days without looking at my calendar. That is the point at which I despaired of reproducing the problem.

Since I can't reproduce the problem, I see no point in updating my copy of the app.

Activity

  1. added
    bugSomething is not working
    needs triageIssue is not yet ready for PR authors to take up
    on Oct 26, 2026
  2. fossifybot commented on Oct 26, 2026

    @fossifybot
    Contributor

    One or more required checklist items are unchecked. Please edit the issue body to complete the checklist.

  3. added
    waiting for authorIf the author does not respond, the issue will be closed. Otherwise, the label will be removed.
    on Oct 26, 2026
  4. JperiodMichael commented on Oct 27, 2026

    @JperiodMichael
    Author

    I don't understand how one or more required checklist items can be unchecked when the bug submission supervisor wouldn't let me submit the bug report until I checked all required checklist items.

    How do I go about getting the fossifybot to tell me which item(s) it thinks remain unchecked?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is not workingneeds triageIssue is not yet ready for PR authors to take upwaiting for authorIf the author does not respond, the issue will be closed. Otherwise, the label will be removed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions