Has anyone noticed the debug.log that is generated when you run a published storyline file locally? The file is created in the storyline publish folder when you run the story.html and then close the browser after a few slides. This has started to happen in the last few days. The latest version Version 81.0.4044.122 (Official Build) (64-bit) was also released about then.
This has started to happen on all storyline 360 and storyline 2 files run locally on Chrome but not in Firefox or edge
I have attached the file that is generated and the folder that the file was launched from. Doug
I tried running a few tests on my end with a sample course I created, but I am not showing a debug.log file appearing. I will launch the course locally in Chrome (version 81.0.4044.122), and after viewing a few slides, the local files remain the same.
May I ask if you could share how the course is being published and possibly a screen recording of your workflow? This would help out greatly as we continue to get to the bottom of this!
1 Reply
Hi Doug,
Thank you for reaching out!
I tried running a few tests on my end with a sample course I created, but I am not showing a debug.log file appearing. I will launch the course locally in Chrome (version 81.0.4044.122), and after viewing a few slides, the local files remain the same.
May I ask if you could share how the course is being published and possibly a screen recording of your workflow? This would help out greatly as we continue to get to the bottom of this!
This discussion is closed. You can start a new discussion or contact Articulate Support.