Black screen with loading dots

I have been through the overall results slide and deleted elements until the navigation worked. It seems what is causing the issue is the variable references I have used on the slide to refer to each section's activities. Attached is a screenshot of an example.

Why would the variables references be causing this issue?

 

yes it happens for me also (checked with Chrome)

https://360.articulate.com/review/content/6f7adbe7-9f8d-46a3-a782-d146bd3b0b68/review

a peek with the result

https://360.articulate.com/review/content/1167b909-3337-4e4f-b399-172c62731872/review

and I get many errors in the browser console

many (> 50):

• Uncaught TypeError: Cannot read properties of null (reading 'el')

then

• Uncaught TypeError: Cannot read properties of null (reading 'componentWillReceiveProps')
• Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the AccText component.
• Uncaught Invariant Violation: findComponentRoot(..., .1.0.1.0:$_player=16CxZNxEGPOu=1675S9n5iqJR): Unable to find element. This probably means the DOM was unexpectedly mutated (e.g., by the browser), usually due to forgetting a <tbody> when using tables, nesting tags like <form>, <p>, or <a>, or using non-SVG elements in an <svg> parent. Try inspecting the child nodes of the element with React ID ``.
• ...

it happens on Review 360 with Chrome (Firefox not tested)

I have added the link to Review 360 in my first post

please open a support case with a link to this thread

(the error messages are not for you, they are for the articulate support)

@support: after around 30 minutes of waiting, the 3 dots animation disappeared - but the main menu is not working

@support: the browser log file is the attachment

Hi Hannah,

I'm happy to chime in, and I appreciate the help of Jürgen here as well!

Good job isolating the variable references causing the issue, Hannah! I ran some tests on the Storyline project and found that the variable references in slide 8.8 use built-in variables not used by the other Result slides. This causes the freezing issue as Storyline cannot associate the variable references. I replaced the variable references with the correct ones, and it fixed the problem. You may need to update the variables in the triggers in slide 8.8 as well for the course to function properly.

I'm unsure where the variable versions with a '1' came from; they could've been generated by copying and pasting Result slides. I attached the revised Storyline project with this fix.

Please let me know if you have any questions!

Thanks Eric.  This helped me too.  I had used an old course/template to create a new one and when I got to the Results slide I was missing a few things and had a few not working.

1 - I had to ensure the quiz was tracking/scoring the correct "new" questions

2 - I had to ensure my triggers were using the new quiz variables.  To help with this I renamed the quiz  (on the results slide, design, quiz settings, name.... the name here copies over to the built-in variable so it was easier to locate instead of results.scorepercent and results1.scorepercent.  My new quiz name "final_quiz" came up in the variables list as final_quiz.scorepercent.)

3 - I had variables inserted on my slide "here is the score you got" and they were pointing to the old (template's) results.scorepercent instead of the new quiz (final_quiz.scorepercent) I had just created.

(hope that makes sense)