Bug: Fullscreen notification is not working

[roeniss]

macOS version

14.6.1(23G93)

MeetingBar version

4.10.0

Installation source

Homebrew

Calendars provider

Google Calendar

Bug description

After checking "Show a fullscreen notification" and selecting "when the event starts", it doesn't show up when the event started.

I think this is specifically a bug of the feature because "Send a system notification" is working well with the same settings.

Reproduction steps

I found this bug right after installation.

Expected behavior

Shows a fullscreen notification on time.

Screenshots/screen recordings

Additional context

I tried to turn on "Show a fullscreen notification" solely just in case but no luck.

[dosubot]

Hey @roeniss! 👋 I'm here to help you with any bugs, questions, or contributions related to MeetingBar. Let's tackle this fullscreen notification issue together!

I found a similar open issue that might be related to the problem you're experiencing: Bug: Fullscreen notifications not displayed for short events in quick succession. This issue suggests that the problem might be related to how MeetingBar processes and schedules notifications, especially for events that are scheduled closely together. It recommends checking the notification settings to ensure they are correctly configured and that the alert style is set to allow fullscreen notifications.

Additionally, there are specific conditions in the code that could prevent fullscreen notifications from being displayed:

1. Screen Locked: Notifications won't show if the screen is locked.
2. Fullscreen Notification Not Activated: Ensure that the fullscreen notification feature is activated in the settings.
3. Event Timing: The notification is only triggered if the event is within a specific time interval before it starts ^[1].

You might want to verify these conditions to ensure they are not affecting the display of fullscreen notifications.

To continue talking to Dosu, mention @dosu.

[roeniss]

After the first day, it shows well now. Don't know why, but issue seems resolved to me.