[BUG] device.destroy throws in Chrome extension workers

[andr-smrnv]

• I have verified that the issue occurs with the latest twilio.js release and is not marked as a known issue in the CHANGELOG.md.
• I reviewed the Common Issues and open GitHub issues and verified that this report represents a potentially new issue.
• I verified that the Quickstart application works in my environment.
• I am not sharing any Personally Identifiable Information (PII)
  or sensitive account information (API keys, credentials, etc.) when reporting this issue.

Code to reproduce the issue:
Use device normally somewhere in the context of a browser extension worker (v3)

import { Device } from '@twilio/voice-sdk'

const device = new Device(token)
await device.register()
device.on('unregistered', () => {
  device.destroy() // throws
})

// we unregister when the user logs out
await device.unregister()

Expected behavior:

Device unregisters normally and closes its WS connection. When creating a new device in the same runtime context, everything works correctly and we're able to receive inbound calls.

Actual behavior:

device.destroy() throws, and even if we create a new device it's no longer capable of receiving inbound calls.

More specifically, this place:

twilio-voice.js/lib/twilio/audiohelper.ts

Lines 427 to 429 in 41e4412

	if (!this._mediaDevices || !this._enumerateDevices) {
	throw new NotSupportedError('Enumeration is not supported');
	}

This kinda makes sense, because we grab _mediaDevices from navigator.mediaDevice, which is undefined in the worker, but it probably doesn't make sense to throw it then.

I had to patch it on my end, just by replacing the error with the return statement, but I'm not sure it's the best solution.

---

This is the error that happens after we create a completely new device and try to receive an inbound call:

I suspect this happens because the first exception interrupts the cleanup procedure and some stale references remain.
Software versions:

• Chrome 132
• MacOS Sequoia 15.2
• @twilio/[email protected]

[kpchoy]

@andr-smrnv thanks for submitting. I'll submit an internal ticket to track this issue.