-
Notifications
You must be signed in to change notification settings - Fork 5.1k
CORS issue with 1.2.0 on Firefox and Safari #2978
Comments
Is there a fix in sight, this isn't the first time this issue has come up. It was in earlier versions as well. Is anyway we can get a client test in place to send a test call to infura from webkit before a release? You could use something like phantomJS or another headless webkit testing framework. |
this is pretty serious guys |
@felixwatts Just leaving a note - it looks like this is fixed on the 2.0 branch with #2564. Will prioritize back-porting that to 1.x but it could still be a bit before it makes it to a published patch. |
@cgewecke I will back port this fix this week to include it in the next release. @felixwatts The next version will be published after devcon when I‘m back home. |
I can't install 1.2.2 version. I tried with node versions: 10.16.3, 12.10.0, 12.13.0, 13.1.0 |
Can you post the errors you are getting @davidtacer? Or better yet, open another issue with them? Thanks! |
Steps to reproduce:
var web3 = new Web3(new Web3.providers.HttpProvider('https://rinkeby.infura.io/'));
web3.eth.getTransaction('0xd540f813d46953f5bf7c0b3797572ff6b73eee0eeadfac071baee0da9a7a9b5a').then(console.log);
You will get the following error messages:
Doesn't happen on Brave or Chrome or the new Edge, but happens on Firefox, Safari and Safari Mobile.
The text was updated successfully, but these errors were encountered: