Skip to main content
Participating Frequently
September 20, 2016
Question

Captivate 9.0.2 + iOS 10 Audio not playing

  • September 20, 2016
  • 12 replies
  • 6665 views

Hi,

I've had SCORM courses working on an LMS for the past year with no issues. All have audio voiceovers and small videos in place. Now that iOS 10 has launched, the voiceovers don't play and the videos are skipped instead of downloaded. I haven't changed these course files so it appears something is no longer compatible in the new iOS and is affecting the playback of these courses. They work fine on a desktop, but not on an iPad or iPhone with iOS 10. (Wasn't an issue with iOS 9).

Has anyone else experienced this?

I don't think it has to do with the Cap 9 update since the files were created in the original 9 and were fine. I've tested a 9.0.2 file and it's the same result so it appears something amiss with how iOS 10 is handling the course files.

Any thoughts or advice?

Thanks so much,

Lisa

This topic has been closed for replies.

12 replies

adtiwari
Adobe Employee
Adobe Employee
September 21, 2016

Hi Lisa,

I verified sample 902 content on ios 10, for an Iphone 6 as well as ipad pro. Audio and video seemed to be working fine. I have hosted sample content on a webserver http://trycpcontent.com/leadgen_902/. You can verify if that works fine for your ios device.

Moreover, can you send me one of your sample content created out of cp 902 and share it(via dropbox) to CaptivateHelp@adobe.com?

Thanks,

Aditya

LeDesignAuthor
Participating Frequently
September 21, 2016

Hello Aditya,

I tested your sample content on my iPhone and iPad and it is indeed working. I will upload my files for you… perhaps I've got a setting or preference or something off?

Thanks so much for your help,

Lisa

adtiwari
Adobe Employee
Adobe Employee
September 22, 2016

Hi Lisa,

  I can hear the audio fine for the project you sent. Can you check your audio settings once ?

Thanks,

Aditya

RodWard
Community Expert
Community Expert
September 21, 2016

This sort of problem is always a possibility when there is some major change to an OS in a mobile device platform.

I suggest you log it as a bug with Adobe.  They may already be aware of the issue but your specific use case will help them work out what to do.

After that you may have to wait patiently for a fix of some kind.

Hopefully someone else here will have found a workaround.

LeDesignAuthor
Participating Frequently
September 21, 2016

Thanks Rod, I always appreciate your response and advice.