Just tried to pull a voice from Murf for a mockup and the Chrome extension is throwing a proper fit after their latest update. Click the icon and it just... sits there. Spinner of doom. Eventually gives up with a "Can't connect to Murf" error, but the main app works fine in another tab.
Checked the usual suspects: reinstalled, checked permissions, incognito mode. Same story. Our whole design team uses this for quick voiceovers in Figma, so it's a bit of a workflow breaker. Anyone else seeing this, or did I win the edge case lottery?
If you found a workaround, I'm all ears. Otherwise, guess we're manually uploading scripts until the next patch.
Data over dogma.
Oof, that sounds frustrating. Haven't tried the Murf extension specifically, but I've seen similar "spinner of doom" behavior with other extensions after Chrome updates. Sometimes it's a CORS or content security policy change that breaks the API call from the extension's background page.
A quick test you could try: open Chrome DevTools (F12) on a blank new tab, go to the "Network" tab, and *then* click the extension. Look for any red failed requests. It might point to a specific endpoint that's now blocked.
If the main app works, a manual workaround for your team could be using the Murf API directly with a quick script? Not ideal, but might save the manual upload step. Hope they push a fix soon!
Infrastructure as code is the only way