Bug: Alarms are not saved to database when pressing Save (AlarmModel remains empty)

[srykaran]

Description

When creating or updating an alarm on Android, the alarm is not saved to the ISAR database, and therefore it does not appear in the alarm list or ring at the scheduled time.

After pressing Save, the UI sometimes closes or returns to the previous screen, but the alarm is not persisted.

Using the Isar Inspector, the AlarmModel collection remains empty, which causes the scheduler to cancel alarms because it cannot detect any upcoming alarms.

Steps to Reproduce

1. Run the application on a physical Android device.
2. Open the Add Alarm screen.
3. Set any valid alarm time.
4. Tap the Save button.
5. Return to the home screen.

Expected Behavior

The alarm should be saved to the database and immediately appear in the alarm list.
The alarm should also be scheduled and ring at the selected time.

Actual Behavior

• The alarm does not appear in the alarm list.

• No record is created in the AlarmModel collection.

• The alarm never rings.

Logs

During debugging the following logs appear:

STOPPED IF CONDITION with latest = TimeOfDay(...)

FLUTTER CALLED CANCEL ALARMS

This indicates that the scheduler cannot find any upcoming alarms and cancels scheduling.

Database Observation

Using Isar Inspector, the database state shows:

AlarmModel = 0 records

This confirms that the alarm is not being persisted after pressing Save.

The screenshot shows that other models (RingtoneModel, ProfileModel) exist,
but AlarmModel remains empty after pressing Save.

Screenrecording

This screen recording demonstrates that after pressing Save, the alarm is not added to the list and no record is created in the ISAR database.

WhatsApp.Video.2026-03-14.at.1.04.10.AM.mp4

Environment

Flutter version: 3.22.2 (via FVM)
Platform: Android
Android SDK: 34
Device: Physical Android device

I would like to work on fixing this issue if it is confirmed.

[srykaran]

I implemented a fix that now allows alarms to be saved to the ISAR database
and appear correctly in the alarm list.

However, during testing I noticed that alarms do not automatically ring when
their scheduled time arrives. The ringtone only plays when using the Preview
Alarm feature.

The alarm persists after restarting the app, so the database part appears fixed,
but the scheduling/trigger mechanism may still not be firing correctly.

I will continue investigating the scheduling logic.

[srykaran]

Update: The alarm saving issue appears to be fixed by the PR linked above.

However, during further testing I noticed that alarms still do not ring automatically when the scheduled time arrives. The ringtone only plays when using the Preview feature.

Since this seems to be a separate scheduling/trigger issue, I will open a new issue to track it separately.