-
Notifications
You must be signed in to change notification settings - Fork 33
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
Unable to fetch feature toggles DOMException: signal is aborted without reason #165
Comments
We're aware of this: Unleash/unleash-proxy-client-js#183. A few people reported seeing those error so we'll be looking into this today. |
Thank you @kwasniew! |
@nmaties can you confirm if https://github.com/Unleash/proxy-client-react/releases/tag/v4.2.3 fixes your issue? |
Give me some time, I'll check it and reply here. @kwasniew |
@kwasniew I am still able to reproduce it with v4.2.3 |
@nmaties can you fork and edit my blitz https://stackblitz.com/edit/react-flags-demo?file=src%2FApp.js to help me diagnose the issue? I prepared a starter project reading a flag from a demo account and doing a basic check. |
Also I updated peerDependency version in 4.2.4 if you didn't install unleash-proxy-client dependency manually and depended on auto install. |
Describe the bug
Hello there,
I keep on getting the following error in the browser:
Has anyone else experienced this?
Do you know how I can fix it?
Using version: ^4.1.1 in the package.json
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
^4.1.1
Subscription type
None
Hosting type
None
SDK information (language and version)
No response
The text was updated successfully, but these errors were encountered: