Skip to content

AlarmInfo Inconsistences #9447

@murilopereirame

Description

@murilopereirame

When deleting an event, removing an alarm or deleting a calendar, alarms are not being removed.
We must identify where the delete code for alarms isn't being executed, fix and clean up orphan alarms.

Test notes

Cleanup

  • Create two events with reminders (event1 and event2)
  • Login on desktop and android (not sure but iOS reminders are hard to test on test system) so that reminders are scheduled on these devices
  • Turn them into orphan reminders (using broken server version e.g. tutadb-release-303.250807.0)
    • event 1: Remove alarm and save event (so only the reference from Event to UserAlarmInfo is not there)
    • event 2: Remove reminder and save event, delete event (UserAlarmInfo exists, but event is deleted )
    • verify user alarm info state with admin client
  • Run CleanupInconsistentUserAlarmInfosBatchJob job and verify that the 2 user alarms infos are getting deleted
  • Verify that unschedule messages are received by android and desktop client and that the reminders are not scheduled anymore.

Fix

  • Create two events with reminders (event1 and event2)
  • Login on desktop and android so that reminders are scheduled on these devices
  • Use up-to-date server to test the fix
    • event 1: Remove alarm and save event, alarm should be unscheduled
    • event 2: delete event, alarm should be unscheduled

Sub-issues

Metadata

Metadata

Labels

bugbroken functionality, usability problems, unexpected errorsstate:testedWe tested it and are about to release it

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions