prajakti
03/25/2025, 7:16 PMdaily-co/react-native-webrtc
(I tried both 118.0.3-daily.1
and 118.0.3-daily.2
). Any idea what I might be doing wrong or how I can debug?
│ LOG MediaDevices _registerEvents invoked │
│ ERROR TypeError: WebRTCModule.startMediaDevicesEventMonitor is not a function. (In 'WebRTCModule.startMediaDevicesEventMonitor()', ││'WebRTCModule.startMediaDevicesEventMonitor' is undefined)
Vapi Support Bot
03/25/2025, 7:17 PMWebRTCModule.startMediaDevicesEventMonitor
error you're encountering, but I can definitely help with some troubleshooting steps that might resolve your issue.
Here are some debugging steps that might help:
## Dependency and Version Checks
First, make sure your dependencies are correctly installed and compatible:
json
{
"dependencies": {
"react": "18.2.0",
"react-native": "0.73.6",
"@vapi-ai/react-native": "^0.1.2"
},
"devDependencies": {
"@babel/core": "^7.20.0"
}
}
According to the information I found, it's important to check that all required dependencies and versions are correctly installed in your project [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510).
## SDK Version Compatibility
The error you're seeing might be related to SDK compatibility issues. If you're using Expo, try downgrading to Expo SDK 50, as this has resolved similar issues for other users [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510).
## General Debugging Steps
Here are some additional debugging techniques that might help:
1. **Clear Metro Bundler Cache**: Run npx react-native start --reset-cache
to clear the Metro bundler cache.
2. **Rebuild the App**: After making changes, completely rebuild your app with npx react-native run-android
.
3. **Review Recent Changes**: If the setup was previously working, review any recent changes to the project or its dependencies.
4. **Check Vapi Instance Creation**: Ensure the vapi
instance is created correctly without any conditional dependencies.
5. **Use useRef**: Try using useRef
instead of a regular variable to ensure the Vapi instance persists between renders.Vapi Support Bot
03/25/2025, 7:17 PMVapi Support Bot
03/25/2025, 7:18 PMWebRTCModule.startMediaDevicesEventMonitor
error you're encountering, but I can definitely help with some troubleshooting steps that might resolve your issue.
## Dependency and Version Checks
Make sure your dependencies are correctly installed and compatible:
json
{
"dependencies": {
"react": "18.2.0",
"react-native": "0.73.6",
"@vapi-ai/react-native": "^0.1.2"
},
"devDependencies": {
"@babel/core": "^7.20.0"
}
}
According to the [troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510) I found, it's important to check that all required dependencies and versions are correctly installed.
## SDK Version Compatibility
If you're using Expo, try downgrading to Expo SDK 50, as this has resolved similar issues for other users according to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510).
## General Debugging Steps
Here are some additional debugging techniques that might help:
1. **Clear Metro Bundler Cache**: Run npx react-native start --reset-cache
to clear the Metro bundler cache.
2. **Rebuild the App**: After making changes, completely rebuild your app with npx react-native run-android
.
3. **Review Recent Changes**: If the setup was previously working, review any recent changes to the project or its dependencies.
4. **Check Vapi Instance Creation**: Ensure the vapi
instance is created correctly without any conditional dependencies.
5. **Use useRef**: Try using useRef
instead of a regular variable to ensure the Vapi instance persists between renders.
6. **Check Network Connectivity**: Verify that your device or emulator can reach the necessary servers.Vapi Support Bot
03/25/2025, 7:18 PMVapi Support Bot
03/25/2025, 7:19 PMWebRTCModule.startMediaDevicesEventMonitor
error you're encountering. However, I can definitely help with some troubleshooting steps that might resolve your issue.
Here are some debugging steps that might help:
## Dependency and Version Checks
First, make sure your dependencies are correctly installed and compatible:
json
{
"dependencies": {
"react": "18.2.0",
"react-native": "0.73.6",
"@vapi-ai/react-native": "^0.1.2"
},
"devDependencies": {
"@babel/core": "^7.20.0"
}
}
According to the information I found, it's important to check that all required dependencies and versions are correctly installed in your project [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510).
## SDK Version Compatibility
The error you're seeing might be related to SDK compatibility issues. If you're using Expo, try downgrading to Expo SDK 50, as this has resolved similar issues for other users [source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1239945056937443510).
## General Debugging Steps
Here are some additional debugging techniques that might help:
1. **Clear Metro Bundler Cache**: Run npx react-native start --reset-cache
to clear the Metro bundler cache.
2. **Rebuild the App**: After making changes, completely rebuild your app with npx react-native run-android
.
3. **Review Recent Changes**: If the setup was previously working, review any recent changes to the project or its dependencies.
4. **Check Vapi Instance Creation**: Ensure the vapi
instance is created correctly without any conditional dependencies.
5. **Use useRef**: Try using useRef
instead of a regular variable to ensure the Vapi instance persists between renders.Vapi Support Bot
03/25/2025, 7:19 PMVapi Support Bot
03/25/2025, 7:19 PMWebRTCModule.startMediaDevicesEventMonitor
error more effectively.
In the meantime, if you discover any additional information or if anything changes with your setup, please let us know as it might help in diagnosing the issue faster.
Someone from our team will be in touch with you shortly. Thanks for your patience! 🙏prajakti
03/25/2025, 7:23 PMShubham Bajaj
03/26/2025, 11:18 PM