Forum Discussion
Allowing microphone access on embedded web app
I have embedded a web app into my Storyline via a web object, and do not seem to be able to find any way to allow the Storyline to access the user's microphone.
How do I go about allowing the embedded page to access the user's microphone?
12 Replies
Hi DanAdams-9ad8e6,
Happy to help!
You can try modifying your iframe to add the allow tags and specify the exact permissions you need. Example:
<iframe src="..." allow=”autoplay; microphone”></iframe>
Hope this helps!
Hi, I am experiencing a similar issue. I have a web app that I am running through the web object option in Storyline. When I publish and run in preview I'm getting this message.
"The security policies of this page don't allow using the microphone." I'm unsure if this is related to the page or to Storyline and would appreciate some advice.
Hello DannyMcGee-3972,
Thanks for reaching out regarding the Audio settings message you are receiving when trying to access the microphone. This may be related to the security settings of the hosting website or the browser rather than Storyline itself. I have a few clarifying questions to better understand your setup!
- What web app are you currently using? Can you natively access the microphone for this site when viewing it in a browser window?
- Have you tried modifying the iFrame as my colleague Jose suggested earlier in this discussion?
- From your screenshot, I understand you are using Edge. Do you experience this behavior in another browser? I'm curious if it is browser-specific.
As a first step, here are a few things you can check:- Secure Hosting: Ensure your web app is hosted on a secure website using `https://`. Modern browsers block mixed content, so if your web app uses `http://`, it might be causing the issue.
- Browser Permissions: Check the browser settings to ensure that microphone access is allowed for the site where your web app is hosted.
- iFrame Restrictions: If your web app is embedded in an iframe, ensure the hosting website allows it. Some sites have `X-Frame-Options` set to `SAMEORIGIN` or `DENY`, which can prevent the web object from functioning properly.
If you're still having trouble, we'd be happy to examine your file more closely. You can upload your .story file to this thread or privately in a support case.
Looking forward to hearing from you!
- What web app are you currently using? Can you natively access the microphone for this site when viewing it in a browser window?
Hello,
Thanks for the info - however, I cannot find where these iframes would be added. Where in the package should I be adding these permissions?
Hi DanAdams-9ad8e6,
I'm happy to help!
Could you please share your current iframe code in this thread? It will be helpful to see the existing code along with your .story file in order to recommend placement!
Looking forward to hearing from you!
Hello,
I would love to - if I knew where to find it! Could you please advise on exactly which file the iframe code can be found in? In the meantime, here is the slide/web object in question.
Thanks in advance!
JoseTansengco After some testing and changes I have been able to get an iframe to request microphone access - but it does not transmit the audio from the mic to the iframe. This is happening in both Storyline and Rise.
Is there an iframe setting that should be enabled to allow the transmission of microphone audio to the frame? Thanks in advance.
Hello DanAdams-9ad8e6,
Thank you for sharing where you are in the process!
Do you receive this error message? I'm curious if you are experiencing this same error message.
- I am seeing a Quick Start guide to modifying the API Key that could be helpful.
Looking forward to hearing from you!Hi there,
Thanks for the reply - but no, it is not to do with that unfortunately. That is a response on the part of the app when it is receiving no mic input.
The issue appears to be that the iframe refuses to receive audio - and this occurs on both Rise and Storyline when published as an uploadable LMS package. While it works in Rise's builder and preview it still fails when it is a package uploaded to an LMS.
Any info/solutions are highly appreciated, thank you for your time so far.
