Chrome-Store-Foxified
Chrome-Store-Foxified copied to clipboard
Noitidart
Unhandled error while validating URL: NetworkError when attempting to fetch resource.
For instance if I go to the chrome store and click add to Firefox it switches to the foxified window with that message
On Nov 22, 2017 8:37 AM, "Noitidart" [email protected] wrote:
At which step does this happen?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Noitidart/Chrome-Store-Foxified/issues/100#issuecomment-346368112, or mute the thread https://github.com/notifications/unsubscribe-auth/ABzapE0H5pdkND0zLluQ4Wsic3e3FYo3ks5s5DGhgaJpZM4QmtiW .
Are you using private mode? Like this - https://github.com/Noitidart/Chrome-Store-Foxified/issues/36 - ?
I have tracking protection checked but not in a private session and history set as normal
On Wed, Nov 22, 2017 at 12:24 PM, Noitidart [email protected] wrote:
Are you using private mode? Like this - #36 https://github.com/Noitidart/Chrome-Store-Foxified/issues/36 - ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Noitidart/Chrome-Store-Foxified/issues/100#issuecomment-346434970, or mute the thread https://github.com/notifications/unsubscribe-auth/ABzapIzmujtQzj2DQbjK5u-qNIU6OI8Rks5s5GbkgaJpZM4QmtiW .
Just to test, may you please try disabling any of these security things. Tracking protected might be disabling your cookeis which would break the Foxified.
I had the same problem. Just wanted to confirm that tracking protection being set to "Always" was creating the issue. Changing it to "Never" or "Only In Private Windows" when performing extension installation resolves the problem. I can change it back to "Always" when I'm done installing or updating.
This may be able to be resolved with a whitelist, but I didn't test it.
@ThunderFace Could this be a firefox bug, tracking protection is meant to notify you when its active/blocking with an icon in the URL bar
Disabling tracking protection fixed the issue. Thought I reported back on this sorry.