Are you able to give a little more detail about what's going on? If you'd like, we'd be happy to take a closer look at it. Please submit a case, including your .story file, using this link so our support team can assist you further.
I am going mad actually,all the course what we have created in storyline is having the same problem,and its not happening evreytime. once the timeline ends in the page and user tap on the ipad (any where on the screen) the page is getting reloaded.
Are you also facing the same issue. If yes is there a way to solve this issue. am sorry i cant share the sroyline, its project based course.
Can you tell me if this is happening in HTML5 or with the Mobile Player app? If it's HTML5, can you tell me which browser you're testing it with? Because this doesn't sound like a known issue, we'd probably need to see your file to determine exactly why this is happening, but the more information you can provide, the more help we can offer. Thanks!
ItS also happening in HTML5 output, i have used google chrome,Mozilla for dekstop and safari for iPad.i spend some more time to find why this issue is happening, finally got it but no idea how to fix it,"its because of Seekbar,if you press the seekbar any where in then course then all pages will replay once its end and click on the page"
this error is there in all storyline HTML5 output,i cant share my project file but i just cretaed a dummy file and attached here.
Please take the file and run HTML5 out put in in chrome or mozilla.
Test the file in below way,
First you dont click on the seekbar let the screen finish and click on the page .this time page wont replay, its work fine.
now refresh the page and click on the seekbar and move it any where,wait tell the screen finish once screen finish then click any where on the screen or browser area,then screen start replaying it again.
can you tell me is any option i can fix this issue.
Thanks for following up and posting this. I was able to replicate exactly what you described, and I'm going to go ahead and get it logged with our support team so we can do further testing on it. Thanks again, and someone will be contacting you soon.
Hi again, Sinchu. Just wanted to let you know that the issue has been escalated to our QA team, and as soon as I hear something from them, I'll pass it onto you. Thanks for again for posting this.
Thanks so much, i just wanna make you clear that this issue is happening in all storyline project.it will be great of you guys fix this,i have got a mail for your Customer Support Engineer ,he told me he will get back to me once issue is fixed.
Unfortunately, Sinchu, we weren't able to come up with a solution for this in time for the update. It's still at the forefront of issues we're hoping to get resolved soon, and I'll be sure to have someone contact you as soon as we have something in place for you. Really sorry for the inconvenience, and thanks for your patience.
The Articulate Quality Assurance Team has reported that this problem has been fixed within Storyline Update 5. At your convenience, we'd love it if you'd republish your content using Update 5 and verify for us that the problem has been resolved. Thanks!
11 Replies
Hi Sinchu,
Are you able to give a little more detail about what's going on? If you'd like, we'd be happy to take a closer look at it. Please submit a case, including your .story file, using this link so our support team can assist you further.
Thanks!
HI Peter,
hope you are doing good.
I am going mad actually,all the course what we have created in storyline is having the same problem,and its not happening evreytime. once the timeline ends in the page and user tap on the ipad (any where on the screen) the page is getting reloaded.
Are you also facing the same issue. If yes is there a way to solve this issue. am sorry i cant share the sroyline, its project based course.
Hey Sinchu!
Can you tell me if this is happening in HTML5 or with the Mobile Player app? If it's HTML5, can you tell me which browser you're testing it with? Because this doesn't sound like a known issue, we'd probably need to see your file to determine exactly why this is happening, but the more information you can provide, the more help we can offer. Thanks!
HI Peter,
ItS also happening in HTML5 output, i have used google chrome,Mozilla for dekstop and safari for iPad.i spend some more time to find why this issue is happening, finally got it but no idea how to fix it,"its because of Seekbar,if you press the seekbar any where in then course then all pages will replay once its end and click on the page"
this error is there in all storyline HTML5 output,i cant share my project file but i just cretaed a dummy file and attached here.
Please take the file and run HTML5 out put in in chrome or mozilla.
Test the file in below way,
First you dont click on the seekbar let the screen finish and click on the page .this time page wont replay, its work fine.
now refresh the page and click on the seekbar and move it any where,wait tell the screen finish once screen finish then click any where on the screen or browser area,then screen start replaying it again.
can you tell me is any option i can fix this issue.
Hi Peter,
Here is the source file.
Hey Sinchu!
Thanks for following up and posting this. I was able to replicate exactly what you described, and I'm going to go ahead and get it logged with our support team so we can do further testing on it. Thanks again, and someone will be contacting you soon.
Hi again, Sinchu. Just wanted to let you know that the issue has been escalated to our QA team, and as soon as I hear something from them, I'll pass it onto you. Thanks for again for posting this.
Hi Peter,
Thanks so much, i just wanna make you clear that this issue is happening in all storyline project.it will be great of you guys fix this,i have got a mail for your Customer Support Engineer ,he told me he will get back to me once issue is fixed.
HI Peter, any update regarding this issue? i have tested in v2 also but same error is happening.
Unfortunately, Sinchu, we weren't able to come up with a solution for this in time for the update. It's still at the forefront of issues we're hoping to get resolved soon, and I'll be sure to have someone contact you as soon as we have something in place for you. Really sorry for the inconvenience, and thanks for your patience.
Good Afternoon, Sinchu.
The Articulate Quality Assurance Team has reported that this problem has been fixed within Storyline Update 5. At your convenience, we'd love it if you'd republish your content using Update 5 and verify for us that the problem has been resolved. Thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.