search

vuejs / devtools-v6

⚙️ Browser devtools extension for debugging Vue.js applications.
https://devtools-v6.vuejs.org/
MIT License
24.68k stars 4.14k forks source link

Proxy injection failed #745

Open surruk51 opened 6 years ago

surruk51 commented 6 years ago

Version

3.0.0

Browser and OS info

Chromium 67.0.3396.99 (Official Build) Built on Ubuntu , running on LinuxMint 18.3 (64-bit)

Steps to reproduce

Note: I am actually using v 2.5.17 of Vue as provided by the CDN recommended in the documentation. I do not know how to access a later version.

Link to cdn using as recommended in docs Add chrome extension from vue.js web site Run app until new Vue(....) is executed Go to Vue panel (which by the way is not immediately visible in the diagnostics pane, and also the V icon appears disabled and reports Vue.js not loaded) Error report at top of screen "Proxy injection failed. Vue diags panel is empty.

What is expected?

The Vue diagnostic panel should open with no errors. What it should actually contain, I am not sure as I am new user and find no docs on this, but hope it would report the state of Vue elements etc.

What is actually happening?

The panel is empty and the 'Proxy injection failed' message appears at the top of the panel.

First attempt to use the Vue.js debugging tools. I am new to Vue.js.

Akryum commented 6 years ago

Taking a look at this issue, try restarting your browser.

OzanKurt commented 5 years ago

It doesn't work...

entepe85 commented 5 years ago

This issue also persists with Firefox Nightly (current build: 69.0a1 (2019-07-01)) after entering Responsive Design Mode through the developer tools and refreshing the page.

Vue devtools version: 5.1.1 Vue version: 2.6.10

EDIT: This error pops up in the browser debugging console, when the addon warns about the failed proxy injection:

09:19:54.386 Unchecked lastError value: Error: No matching message handler              background.js:1
entepe85 commented 5 years ago

Disabling other add-ons, refreshing my profile and reinstalling Firefox didn't fix the issue. The addon works in Firefox Beta / Developer Edition (68.0b14), though - even in Responsive Design Mode.

entepe85 commented 5 years ago

This issue persists in FF Developer Edition which has just today been updated to 69.0b1. The addons was working flawlessly in the last beta / developer edition release in the 68 branch of Firefox.

entepe85 commented 5 years ago

As mentioned in the corresponding Bugzilla bug report, both refreshing the browsers and using a clean profile with no additional extensions did not solve the issue.

entepe85 commented 5 years ago

To give some follow-up concerning the error in Firefox: Some event handling related things were refactored in the 69 branch thus breaking several addons in RDM.

entepe85 commented 5 years ago

Issue is fixed for Firefox Nightly 70.0a1 (2019-07-25)