HELP! Engage interaction trouble in Storyline

Update....I saved the file to a flash drive, and gave it to a coworker. She was able to open the storyline file and the engage item showed perfectly after publishing. Soooooooo a couple of thoughts:

1. There are 3 engage items in the course, the other 2 in other scenes....and they have been displaying after each publish on my computer, even when the 1st one in scene 1 doesn't
2. Could this be an issue with pop-up blockers or cache?
3. Why would it display in preview and not once published?

Angel

Ok, I've figured out the problem.  GOOGLE Chrome!

During the day I had installed GOOGLE Chrome, and it doesn't (apparently) display the Engage Interactions. When I opened up the same file in IE, it worked fine.

Thanks!

Angel

Hi Angel,

Thanks for updating us that you were able to get this up and running, and I wanted to point you to this older kb article about a Chrome bug that was interfering with Engage interactions. You'll want to test your published output within it's intended environment, as testing locally can cause some items to display incorrectly due to local security restrictions. 

I know this is an old thread but I am having an issue with an Engage 13 FAQ not displaying in Storyline 2 when viewed on the iPad. I used the insert Engage option (not the web object). This is the first time I have used Engage within Storyline so I am wondering if  anyone has a workaround or if this is a known issue.

I could try recreating the interaction within Storyline itself but my client wanted a fast cost-effective way to do these interactions and suggested Engage as an option.

Is the engage interaction not publishing to HTML5?

I hope it works as I suggested an engage glossy as a web object to a client 

Hmm, I did not publish it because the insert uses the .intr file. I will check the settings.

Update, I just checked the publish settings and they are set to html5

Just tried publishing again - this time using the iOS player settings and it still did not display.  I am going to try inserting as a web object to see if that works. This is such a pain.

Seems to work if you insert as a web object instead of using the import Engage option.

Hi Nancy and Phil,

You'll need to use the Insert as Web object option for Engage element, as inserting it using the "Insert Engage" doesn't pass the same information allowing Engage to know if it should display the Flash, HTML5 or mobile player version. You can read a bit more about how to use the web object method here. 

Thanks Ashley, I suggest removing the import feature if I you can't get it to work properly because this was a real time waster. 

Thanks Nancy for the suggestion - and it does work if you'll be using the Flash output, but maybe it does need to be better indicated that doing so will only work in Flash.