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

SCORM tracks are stored in wrong SCO when using LMSFinish

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • 4.3.0
    • 4.2.0
    • SCORM add-on
    • Hide

      The fix introduced in this issue is covered by behat, no manual testing needed.

      We'll test that everything works as expected during the QA process previous to the release.

      Show
      The fix introduced in this issue is covered by behat, no manual testing needed. We'll test that everything works as expected during the QA process previous to the release.
    • MOODLE_402_STABLE
    • MOODLE_403_STABLE
    • Moodle Apps - 2023 Sprint i3.3

    Description

      Most of the SCORMs we tried use the function LMSCommit to send the data to the server. However, when adding behat tests for SCORM packages in the app I used the RuntimeMinimumCalls_SCORM12-mini package, and this one sends the data in the LMSFinish function when the SCO is unloaded (the next SCO loads). 

      The app uses the current SCO ID when sending the data. In this case, since the SCO has already changed when the LMSFinish function is called, all the tracks (data) is sent using the new SCO ID instead of using the ID of the SCO that generated the tracks.

      Attachments

        Issue Links

          Activity

            People

              dpalou Dani Palou
              dpalou Dani Palou
              Noel De Martin Noel De Martin
              Noel De Martin Noel De Martin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Clockify

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