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

Stop returning isTrusted response #1147

Closed
imolorhe opened this issue Jan 1, 2020 · 4 comments
Closed

Stop returning isTrusted response #1147

imolorhe opened this issue Jan 1, 2020 · 4 comments
Milestone

Comments

@imolorhe
Copy link
Collaborator

imolorhe commented Jan 1, 2020

Return server error response, and a generic error instead of isTrusted: true,

@unstable-cloud
Copy link

unstable-cloud commented Jan 2, 2020

same issue for me....

i'm facing in chrome and firefox extension

@imolorhe
Copy link
Collaborator Author

imolorhe commented Jan 2, 2020

@unstable-cloud This issue is more of an improvement, and is not a bug in Altair. If you get this error, that means you have some generic error (mostly network related) and Altair wouldn't be able to give more context on it. You would need to check either the console, or your server to get more information.

@unstable-cloud
Copy link

unstable-cloud commented Jan 3, 2020

my console

Access to XMLHttpRequest at 'http://localhost/magento2/graphql' from origin 'chrome-extension://flnheeellpciglgpaodhkhmapeljopja' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
main.172f10e….js:1 
t {headers: e, status: 0, statusText: "Unknown Error", url: "http://localhost/magento2/graphql", ok: false, …}
main.172f10e….js:1 Backend returned code 0, body was: [object ProgressEvent]


but
it was working in chromeiql

edit :
before altair version worked

after update showing like that

@imolorhe
Copy link
Collaborator Author

imolorhe commented Jan 3, 2020

There was some permission change in the extension. It would be resolved in the next version. Check #1136 here for more information.

@imolorhe imolorhe added this to the v2.4.3 milestone Jan 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants