Hi Bernd,
the paths look ok in the manifest, I don't know why they're rendered wrong. Maybe the
SCORM engine (the
Javascript code) is processing them and it converts them to backslash. I'm just guessing, but for some reason some slashes are converted to backslashes.
It doesn't happen only in the app, if I open the SCORM in browser and I inspect one of the images I also see them with backslashes:
This screenshot is in Chrome for MacOS. Standard browsers are able to handle those URLs fine (even Safari for iOS), but apparently the app isn't able to.
If the SCORM works fine in Moodle Mobile 3.5 then I guess it must be because of the new WebView. A few years ago Apple released a new WebView named WKWebView (a WebView is like a browser embedded in an app), and in Moodle Mobile 3.9 we stopped using the old one and started using WKWebView because it was mandatory to be able to publish iOS apps. Also, we use a Cordova plugin that fixes some issues when loading local files in this new WebView. So my guess is that UIWebView (the old one) was able to handle backslashes fine, but either WKWebView or the Cordova plugin doesn't. I'm sorry if I was too technical
If you created the SCORM using some tool maybe you can contact the developers of the tool and ask them why are those paths using backslashes and how can it be fixed.
I'll also check if there is any way to make the app support backslashes.
Cheers,
Dani