Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-2814

Update local-notifications plugin

XMLWordPrintable

    • Hide

      This issue needs to be tested both in Android and iOS.

      1. In Moodle web as admin, go to Calendar and create a Site event to happen in 1 hour and a few minutes.
      2. Install the app in a device, login in that site, open that calendar event and verify that the reminder is set to 1 hour before.
      3. Navigate to somewhere else in the app (e.g. a course).
      4. Wait until it's 1 hour before the event. Check that a notification is displayed.
      5. Click the notification. Check that the event is opened.
      Show
      This issue needs to be tested both in Android and iOS. In Moodle web as admin, go to Calendar and create a Site event to happen in 1 hour and a few minutes. Install the app in a device, login in that site, open that calendar event and verify that the reminder is set to 1 hour before. Navigate to somewhere else in the app (e.g. a course). Wait until it's 1 hour before the event. Check that a notification is displayed. Click the notification. Check that the event is opened.
    • MOODLE_36_STABLE
    • MOODLE_36_STABLE
    • Moodle Mobile 3.6.1

      The local-notifications plugin was updated a while ago with some breaking changes. We should update it and adapt the app to the new version.

      Also, we should check if this new version triggers the click event when the app isn't running (dead, not in background). Right now it doesn't, so we don't know that the notifications was clicked.

            dpalou Dani Palou
            dpalou Dani Palou
            Albert Gasset Albert Gasset
            Juan Leyva Juan Leyva
            Isabel Renedo Rouco Isabel Renedo Rouco
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.