Forum Discussion
Need Help to debug an interactive page
I have build an interactive page with multiple click and variable. One click navigates user to another screen and from that screen user loops back to this screen.
The issue is, page gets "not responding" error when I try to visit the screen jump click couple of time.
console shows:
slides.min.js:2 Uncaught TypeError: Cannot read properties of undefined (reading 'accIdx')
resolver::resolvePath - Path did not resolve at: _state
Thanks!
Hi Pankaj,
I'm sorry you're getting this error! After doing a little research, it looks like this may be a JavaScript error. Are you using JavaScript coding on your interactive page? If you are, I'll leave you in the hands of our very capable E-Learning Heroes community. Many members of the community are well-versed in JavaScript.
Thanks for reaching out!
not using JavaScript.
Hi Pankaj,
We would love to troubleshoot this for you! Would you be willing to share your file here or with our support engineers privately in a support case?
Thanks for the reply!
Case submitted along with SL file.
Thank you!
Hello Pankaj!
I see you've opened a case and you are working with our colleague Luiza. You are in great hands!
We'll continue the conversation over in your support case!
Have a great day and happy developing! ✨
What was the resolution here? Getting the same error and it seems after about a day the issue resolves itself. Can't tell if it's from the CDN and the files being delivered out of order or the code not loading in the correct order.
Hi, Aaron!
Looking at Pankaj's support case, it seems the issue was related to a possible software bug in Storyline 360, version 3.68.28887.0, where a course freezes when there are more than 10 layers on a single slide.
This has since been fixed and you shouldn't be experiencing this in the most up-to-date build of Storyline 360, Build 3.73.30119.0. If you continue to see this error, it would be helpful if you could share your file with our team! You can upload it here or privately in a support case. We'll delete it from our systems once troubleshooting is complete.
