From 35c6288b1f1935b776f04f47a3b9346417c6ffef Mon Sep 17 00:00:00 2001
From: Akash Goswami <52071017+Akashgoswami1@users.noreply.github.com>
Date: Tue, 15 Oct 2024 04:14:38 -0700
Subject: [PATCH] Update faq.mdx

Adding capture device issue FAQ
---
 docs/javascript/v2/how-to-guides/debugging/faq.mdx | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/javascript/v2/how-to-guides/debugging/faq.mdx b/docs/javascript/v2/how-to-guides/debugging/faq.mdx
index 6e85cff44..96c80c07a 100644
--- a/docs/javascript/v2/how-to-guides/debugging/faq.mdx
+++ b/docs/javascript/v2/how-to-guides/debugging/faq.mdx
@@ -240,3 +240,15 @@ const { HMSReactiveStore} = require('@100mslive/hms-video-store');
 
 By implementing one of these workarounds, you should be able to resolve the TypeScript errors and continue using the libraries.
 
+#### How to Address Video and Audio Issues with Capture Devices
+
+1. Check for Conflicting Applications: Ensure that no other applications are currently using your audio and video devices. If you find any, close them and restart your 100ms session.
+
+2. Manage getUserMedia Calls: If you're using the getUserMedia function, be sure to stop it before invoking the 100ms join method.
+
+```
+
+const mediaStream = await navigator.mediaDevices.getUserMedia(constraints);
+mediaStream.getTracks().forEach(track => track.stop());
+
+```