Forum Discussion
Result Slide Miscalculation across Devices
I’m facing an issue where the result is getting miscalculated when the module is viewed on a mobile device, but the score is accurate when viewed on a laptop.
The course is published as SCORM 1.2 and uploaded to an LMS. The result slide is showing an incorrect percentage even when all answers are correct. Additionally, when only one question is answered incorrectly, the score displayed is 80% instead of the expected 93%.
The assessment setup is:
- Total questions: 30
- 15 questions are randomized
- Passing score: 80%
- Tracking: Result slide (Final Assessment)
- All correct answers are assigned 10 points, and incorrect answers are assigned 0 points.
It includes two types of graded questions:
- Hotspot questions — created using Slides → Graded Question → Hotspot. There are two clickable options, and based on selection, correct/incorrect layer is shown.
- Standard graded questions — Multiple choice and True/False using Submit button and correct/incorrect layers.
Points to Remember:
- On laptop, score is calculated correctly
- On Android device (Chrome browser), score is miscalculated
- The same SCORM file is used for both mobile and laptop
Has anyone experienced result slide score calculation differences between phone and desktop?
Could this be related to randomized questions, hotspot question behavior, or the LMS?
2 Replies
breakdance04: Since StevenBenassi said there's an Android/Chrome-related bug with hotspot questions, I suggest you try using Freeform Pick One questions.
Instead of Hotspots, use rectangles with a solid fill set to 100% transparency.
Here's more info about Freeforms: Storyline 360: Converting an Existing Slide to a Freeform Interaction
Hi breakdance04,
Sorry to hear that Storyline results are being miscalculated across different devices.
I can confirm that we have this behavior logged as a bug in Storyline 360. This bug causes:
- Hotspot Question Slides cannot be answered when using the Chrome browser on an Android phone.
I've linked this discussion to the bug report so we can notify you as soon as a fix is ready. In the meantime, as a workaround, we suggest using the Firefox browser if possible. We're only seeing this behavior when using the Chrome browser on Android OS.
Thank you for your patience. I'm sorry if this has been slowing you down!
