Hello,
We are facing the exact same problem but apparently only for iOS devices, so iPads and iPhones. From as far as I've tested using Browserstack, this has been happening since iOS Safari 10, and it's now already on 13... so this is not exactly new. Though most of the complaints I've found on this particular issue on other LMLs, some of them Moodle-based, seem to have started around February or March 2020, so I don't know why this discrepancy...
Regardless, from previous Googling it seems like more and more people have been suffering from this but there is yet no fix on Moodle's side, but I did read somewhere that the Rustici engine (i.e. what powers the SCORM player on Moodle) already has an update for this and I can confirm it, since I tested our SCORM files over at SCORM Cloud and indeed the progress is properly recorded when leaving the SCORM player there.
Someone somewhere suggested turning on the auto-commit setting, but this didn't work for us... I don't know if it just doesn't work or if something needs to be done/enabled on our SCORM files. Oh, speaking of which, our SCORM courses were built on both Captivate 8 and 2019 and for both the progress is never saved, so it's really not a SCORM issue, it should really be on the SCORM player itself somewhere...
From debugging on the browser side, I've seen that, when exiting the SCORM player on Moodle, any other browser sends 3 requests to /mod/scorm/datamodel.php with data relative to the user's progress during that session, but this does NOT happen when on Safari for iOS.
These requests are simply not made on iOS, which would explain why the user's progress is not saved.
Something I've noticed that also only seems to happen on iOS is a bunch of requests to the same file but which apparently doesn't exist. Since I've only seen this happening on iOS, I'm assuming Safari is somehow incorrectly building the path of the file it's trying to get and ends up asking for a file that doesn't actually exist. I don't know if this is somehow related to the saving issue or not...
I thought this would be something that was already solved in more recent versions of Moodle, but I checked the git logs over at https://github.com/moodle/moodle, both on the master branch and on the Moodle 3.8 branch, and found nothing regarding this 🙁. I even thought maybe I missed something, so I made a clean basic installation of Moodle 3.8 and uploaded one of our SCORM courses, but alas, the exact same result. To me this clearly means that is something that has not yet been addressed and I have sadly not yet seen it reported anywhere moodle-specific. At least not in these terms.
I just made a quick search through the Moodle issue tracker and the results were disappointing... The closest I found was https://tracker.moodle.org/browse/MDL-66545 and it was tagged as minor priority issue back in August/September 2019.
Does anyone know of a way to get the devs' attention to this issue? Or any other helpful resource to go to? If this doesn't get addressed I'll be forced to put up a notice saying that our courses are simply not available on iOS. Or at least that users can try them but that their progress will not be saved not will they be able to complete them...