Vue-devtools: [Firefox] "Proxy injection failed" while using Responsive Design Mode.

[Hendriksie]

Firefox: 54.0.1 (64-bit)
Vue,js Devtools: 3.1.6
Vue.js: 2.4.2

When using Firefox Responsive Design Mode, Vue.js Devtools is not initializing.
It's giving me the response: Proxy injection failed.

No error is given in the console, but 3 of our projects that's using Vue is giving me the same response.

One of these projects is using Sentry.io logging and we received an error:

TypeError: can't redefine non-configurable property "__VUE_DEVTOOLS_GLOBAL_HOOK__"

in installHook at line 66:3

Steps to reproduce:

1. Use Vue.js in your application
2. Have the official Vue.js Devtools installed in Firefox
3. Enable Responsive Design Mode
4. Open the Vue.js Devtools tab

[jsvini]

Same issue here:

[ghost]

same here! mine doesn't even work in normal view

[andyedward]

same here!
Vue 2.5.3
Firefox 57

[laphilosophia]

👍 same here

[rdpascua]

I'm having issue with firefox quantum too.

[yasare16]

Chrome: Version 63.0.3239.132
Vue Tools: Version 4.0.0
VueJS: 2.5.13

I've also noticed reloading with command + R(⌘ + R) causes the _Proxy Injection Failed_ error sometimes too. Reloading with the browser button gets it right again, though. Also important to note, my developer tools window is open each time this happens. Happens more often as my project gets bigger.

This seems to be about Firefox but I thought I'd mention there are similar problems in Chrome

[tmladek]

Confirming, still exists in:

Firefox: 57.0.3 (64-bit)
Vue.js devtools: 4.1.3
VueJS: 2.5.13

[simplesmiler]

TypeError: can't redefine non-configurable property "__VUE_DEVTOOLS_GLOBAL_HOOK__" was addressed in 4.1.2, so if this issue still happens, it is unrelated to that error.

[simplesmiler]

I was not able to reproduce in:

Firefox: 61.0.1 (64-bit)
Devtools: 4.1.4

[Hendriksie]

I'm not getting the error anymore using:

Firefox: 62 (64-bit)
Vue,js Devtools: 4.1.4
Vue.js: 2.5.16

yay!

(what is the normal procedure to close issues like these, do I have to do it or a mod?)

[simplesmiler]

Good, glad to the the issue resolved!

[entepe85]

Unfortunately, this error still persists in Firefox Nightly. It always happens after the initial reload in responsive design mode (i.e. when the user agent changes) or after manually reloading in that mode.

Firefox: 69.0a1 (64-bit)
Vue.js devtools: 5.1.1
Vue.js: 2.6.10

Even a complete refresh of Firefox (thus also resetting customized about:config entries) didn't get me rid of this issue.

EDIT: I even cleaned Firefox Nighty from my drive and reinstalled it to exclude other potential causes for this behaviour.

[entepe85]

This is the error message I get upon reloading the tab in Responsive Design Mode (from the browser debugging dev tools):

Unchecked lastError value: Error: No matching message handler

EDIT: Before reloading I get this message in the developer tools console, confirming that the extension is actually working:

10:12:02.890 backend -> devtools 
Array [ {…} ]
background.js:1:1367
10:12:02.962 backend -> devtools 
Array(10) [ {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…} ]
background.js:1:1367
10:12:03.029 devtools -> backend 
Array [ {…} ]
background.js:1:1241
10:12:03.035 devtools -> backend 
Array [ {…} ]
background.js:1:1241

[entepe85]

Please reopen this issue as the problem persists across Firefox Nightly (69.0a1) and Developer Edition / Beta (69.0b1 as of today).

[zkriszti]

Restarting the browser seems to have solved this problem for me. (Firefox Developer Edition 69.0b1)

[entepe85]

Thanks, zkriszti. I tried restarting the browser but with no luck. After restarting the corresponding tab / app reloads in normal mode and upon entering RDM and the subsequent reloading of the app / page (due to touch emulation and user agent changes) I get the same error.

EDIT: Additionally, it seems hardly feasible to have to restart the browser every time I try to debug a Vue app in RDM (e.g. a mobile app developed with Ionic, Capacitor and Vue).

[entepe85]

Bug is fixed in Firefox Nightly 70.0a1 (2019-07-25). Corresponding changes in mozilla-central