Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox: NetworkError when attempting to fetch resource #1779

Closed
glowkeeper opened this issue Jul 15, 2017 · 43 comments
Closed

Firefox: NetworkError when attempting to fetch resource #1779

glowkeeper opened this issue Jul 15, 2017 · 43 comments
Assignees
Labels
stale issues and PRs marked as stale type-bug

Comments

@glowkeeper
Copy link

As per this StackExchange post, I'm getting this error in Firefox:

Error: NetworkError when attempting to fetch resource.
Stack trace:
InvalidResponse@http://localhost:8081/bundle.js line 995 > eval:38:16
RequestManager.prototype.sendAsync/<@http://localhost:8081/bundle.js line 7645 > eval:86:29
MetamaskInpageProvider/self.sendAsync/<@moz-extension://bb21b38e-ca5a-6847-afb3-0e13f721de3f/scripts/inpage.js:168:7
[136]</StreamProvider.prototype._onResponse/<@moz-extension://bb21b38e-ca5a-6847-afb3-0e13f721de3f/scripts/inpage.js:8222:5

It goes away when I disable MetaMask....

@fabdarice
Copy link

same +1

@smlbarnes
Copy link

Me too.

@tmashuang
Copy link
Contributor

Is this a dapp using testrpc or is it running in the cmd line? Also, can you provide the version of testrpc?

@danfinlay danfinlay changed the title NetworkError when attempting to fetch resource Firefox: NetworkError when attempting to fetch resource Jul 17, 2017
@fabdarice
Copy link

@tmashuang, I'm using Ropsten.
It was working fine 4 days ago on firefox, then it suddenly stop working and showing "Error: NetworkError when attempting to fetch resource."

@smlbarnes
Copy link

@tmashuang @fabdarice Same situation for me.

@glowkeeper
Copy link
Author

Mine is a dApp that uses a REACT frontend. Currently, I'm using EthereumJS TestRPC v4.0.1 (ganache-core: 1.0.1), but I'm pretty sure it was happening on TestRPC v3.x, too...

@tmashuang
Copy link
Contributor

Are you able to provide a link to the dapp so I can try to replicate the issue?

@glowkeeper
Copy link
Author

glowkeeper commented Jul 17, 2017

@tmashuang, er maybe. Slight problem is that the newer version of TestRPC is enforcing stricter gas limits, so I'm in the middle of shifting much of the heavy lifting away from Solidity, and into the frontend, where it should be anyway ;)

Having said that, if you're happy using v3.x of TestRPC, I can probably point you at a tagged release in my main GitHub branch that 'should' work and will reproduce the issue...

Either that or wait until tomorrow, and I'll give you access to a working v4 version....

@danfinlay
Copy link
Contributor

I think we should wait until the v4 version, in case that fixed the issue by itself.

@glowkeeper
Copy link
Author

@FlySwatter I'm pretty sure it's still happening with v4.

But okay, give me a little while (a day max'), and I'll get you access to a working version of my dApp that you can use for debugging...

@smlbarnes
Copy link

@glowkeeper
Copy link
Author

glowkeeper commented Jul 18, 2017

@FlySwatter @tmashuang - my dApp's ready for you to use for debugging. Hopefully, you've already received notification that I've added you to the dApp repository. Please feel free to branch and do whatever you must ;)

I've confirmed that if I load Firefox with MetaMask enabled, I get the error. However, the dApp runs error free with MetaMask disabled. To fire the error, please visit the Create FakeNews Object link of the dApp. I 'think' it has something to do with there being an async function running under that link....

Hopefully, the README is enough to get you started, but the software is very early in its development cycle, so the instructions I've written (for getting it all running) are 'probably' inadequate. If so, please ask away...

@qjflores
Copy link

I'm observing the same error.

running a truffle box with contracts on the kovan network

this is the snippet of code that is catching the error

try { web3.version.getNetwork(function(error, result){ if(!error){ console.log(result) if(result==='42'){ dispatch(wrongNetwork(false)) } else { dispatch(wrongNetwork(true)) } } else{ console.log("AppActions.setWeb3") console.log(error) } }) } catch (error) { console.log("AppActions.setWeb3") console.log(error) dispatch(wrongNetwork(false)) }

and the stack trace

Stack trace: InvalidResponse@http://localhost:3000/static/js/bundle.js:54611:17 RequestManager.prototype.sendAsync/<@http://localhost:3000/static/js/bundle.js:43757:30 MetamaskInpageProvider/self.sendAsync/<@moz-extension://559bc4d9-ec4a-4f2f-a9ef-4c444023a17e/scripts/inpage.js:168:7 [136]</StreamProvider.prototype._onResponse/<@moz-extension://559bc4d9-ec4a-4f2f-a9ef-4c444023a17e/scripts/inpage.js:8222:5 wrapped@http://localhost:3000/static/js/bundle.js:233291:25

@gkratoc1
Copy link

gkratoc1 commented Jul 20, 2017

I'm experiencing the same thing and am unable to access the ENS Register with Metamask in Firefox. I haven't made any changes to the browser or anything and it has been a week or more since I used Metamask, but it isn't working now and I get the same error on two different computers. Is this related to the latest extension update?

@danfinlay
Copy link
Contributor

Here's something to try:

Try switching your provider (top left MetaMask menu) to another one and back again.

Is it able to find a connection after?

@qjflores
Copy link

Tried switching between the networks and not able to find a connection

@gkratoc1
Copy link

gkratoc1 commented Jul 20, 2017 via email

@danfinlay
Copy link
Contributor

That's very strange. Will try to debug this soon.

@smlbarnes
Copy link

@FlySwatter Still get the error after switching networks.

@dandyh
Copy link

dandyh commented Jul 24, 2017

Im facing the same problem with Firefox and Metamask. Any update on this?

Thanks

@gkratoc1
Copy link

Yeah switching networks proved to be only a temporary solution for me and it came back quickly, still getting the error and am unable to use MM in Firefox. I installed it on Chrome and it works fine. I have tried uninstalling the plugin and reinstalling it in Firefox and that didn't solve the problem for me. I haven't yet wiped the whole Firefox profile and started from scratch, was hoping to see if anyone else had better luck before going to that extreme.

@macbem
Copy link

macbem commented Jul 31, 2017

Yup, I'm getting the error as well, everything works fine on Chrome though.

@dariusdev
Copy link

any news in this issue? Is someone solving it?

@macbem
Copy link

macbem commented Sep 14, 2017

Still not working 😢

@glowkeeper
Copy link
Author

Bump

@matkam
Copy link
Contributor

matkam commented Sep 19, 2017

Seeing this issue on Firefox with https://demo.micro.raiden.network/fortunes_en

@hschoenburg
Copy link

Firefox + Metamask bump

@interfect
Copy link
Contributor

interfect commented Oct 2, 2017

I'm seeing this issue too, on MetaMask 3.10.8, which I believe includes #2138 (#2138 was never merged).

Here's a WireShark dump of a conversation between MetaMask and my Ethereum node (Parity 1.6.10) at http://10.1.0.8:8545. The web page is trying to do web3.version.getNetwork, and immediately and repeatedly retries if it fails.

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:57:59 GMT
Transfer-Encoding: chunked

POST / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: application/json
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
content-type: application/json
origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Content-Length: 98
Connection: keep-alive

{"id":5248397948271052,"jsonrpc":"2.0","params":["0x420e4c",true],"method":"eth_getBlockByNumber"}HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:57:59 GMT
Transfer-Encoding: chunked

{"jsonrpc":"2.0","result":null,"id":5248397948271052}
OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:02 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:03 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:03 GMT
Transfer-Encoding: chunked

POST / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: application/json
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
content-type: application/json
origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Content-Length: 98
Connection: keep-alive

{"id":5248397948271053,"jsonrpc":"2.0","params":["0x420e4c",true],"method":"eth_getBlockByNumber"}HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:03 GMT
Transfer-Encoding: chunked

{"jsonrpc":"2.0","result":null,"id":5248397948271053}
OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:04 GMT
Transfer-Encoding: chunked

OPTIONS / HTTP/1.1
Host: 10.1.0.8:8545
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type,x-metamask-origin
Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/json
Allow: OPTIONS, POST
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: moz-extension://c2480724-8a32-4afc-a7aa-c1d18a8bf229
Date: Mon, 02 Oct 2017 00:58:05 GMT
Transfer-Encoding: chunked

It looks like its first request goes through fine; it does a CORS preflight check for POST to /, gets an answer it likes, POSTs something like {"id":5248397948271052,"jsonrpc":"2.0","params":["0x420e4c",true],"method":"eth_getBlockByNumber"}, and gets an answer of null wrapped in the appropriate JSON.

But then it does another CORS preflight, this time asking if it can also send the x-metamask-origin header, and the server appears to respond with basically "No I have never heard of that header and it is not allowed". According to the CORS spec, Firefox then can't let MetaMask make the request with that header. MetaMask (or Firefox) doesn't seem to know how to deal with this, so it ends up throwing an error, whereupon my page retries the exact same request to MetaMask, with the same result.

If this really is the problem, it looks like the breaking commit was 68fc360 on July 4, a few days before this bug was reported.

Either Parity and other Ethereum nodes need to be modified to explicitly accept the x-metamask-origin header, or MetaMask needs to be modified to not insist on sending it. MetaMask could either not send the header at all, or could try to send the header initially and fall back to not sending it if the request fails because it is not allowed to be sent by CORS.

interfect added a commit to interfect/metamask-extension that referenced this issue Oct 2, 2017
Requests with this nonstandard header are being blocked by CORS when
made against Parity.

Not sending it ought to fix MetaMask#1779.
@nazimran
Copy link

nazimran commented Oct 2, 2017

I'm getting an error.

@kumavis
Copy link
Member

kumavis commented Oct 2, 2017

related #2138

@ghost ghost removed the ready label Oct 2, 2017
@DaneWiid1
Copy link

I'm getting error in Firefox: NetworkError when attempting to fetch resource in version 3.10.8. Stack trace attached. There is no error when running the same dapp with V3.7.8
stacktrace.txt

@sunify
Copy link
Contributor

sunify commented Oct 10, 2017

@DaneWiid1 should work in 3.10.9

@macbem
Copy link

macbem commented Oct 10, 2017

@sunify confirmed - it's working for me in 3.10.9 on Firefox

@mwaeckerlin
Copy link

I still have the problem in Metamask 5.3.2 on Firefox Quantum 64.0!

Running: Ganache CLI v6.2.5 (ganache-core: 2.3.3) on 127.0.0.1:8545 using:

ganache-cli -d --db ${HOME}/tmp/ganache/db -i 123456

The problem occurs at the javascript line:

await window.ethereum.enable();

So it's not solved…?!?

@mwaeckerlin
Copy link

In Chromium this works, so it is related to Firefox. But in Chromium, I then drop into #3094

@mwaeckerlin
Copy link

The code works without Metamask, so it's definitely a bug in Metamask.

@AchinthyaBhat
Copy link

AchinthyaBhat commented May 3, 2021

I am getting the same error when using metamask on polygon network on ff browser

@kumavis kumavis reopened this May 4, 2021
@11reed
Copy link

11reed commented Jun 17, 2021

@AchinthyaBhat Did you find a way to resolve this?

@iraritchiemeek
Copy link

I got this error in Firefox when my local network port was incorrect in Metamask (8545 instead of 7545).
Fixed by correcting the port.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2023

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added stale issues and PRs marked as stale and removed stale issues and PRs marked as stale labels Sep 4, 2023
Copy link
Contributor

github-actions bot commented Dec 3, 2023

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Dec 3, 2023
Copy link
Contributor

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale issues and PRs marked as stale type-bug
Projects
None yet
Development

No branches or pull requests