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

Activity completion check box

XMLWordPrintable

    • Hide
      1. In the app, login in Mobile 34 using a user different than u2.
      2. Go to Course with SCORMS > Complex packages. Check that the checkbox next to "COPY Multiple organizations..." is not marked.
      3. Now open that SCORM and play it through the end. You just need to use the top-right arrow to move to next SCO while answering the questions displayed.
      4. Once you're done, go back to the section view. Check that now the SCORM is marked as completed.
      Show
      In the app, login in Mobile 34 using a user different than u2. Go to Course with SCORMS > Complex packages. Check that the checkbox next to "COPY Multiple organizations..." is not marked. Now open that SCORM and play it through the end. You just need to use the top-right arrow to move to next SCO while answering the questions displayed. Once you're done, go back to the section view. Check that now the SCORM is marked as completed.
    • MOODLE_35_STABLE
    • MOODLE_35_STABLE
    • Moodle Mobile 3.5.2

      Hello,

       

      When completing a scorm package in Safari or the mobile app for IOS the completion of the activity check box is not automatically checking. This then leaves our users unable to progress onto the next activity due to the way we have applied restrictions. When doing this from a windows or mac it works as expected. Moodle is upto date as of 20th of July. Is this a known issue? 

       

      Regards,

       

      Liam

            dpalou Dani Palou
            TitanIT Titan Airways
            Pau Ferrer Pau Ferrer
            Juan Leyva Juan Leyva
            Berta Maroto Berta Maroto
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:

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