-
Notifications
You must be signed in to change notification settings - Fork 168
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
Explorer is not working #1530
Comments
do i need to install anything? |
No, you don't need to install anything. The explorer is included as an iframe - do you maybe have any privacy plugins installed that might block that iframe? |
my browser is clean installed |
@Arian8Ultra can you right-click in the extension and "Inspect"? This should bring up another devtools pane that lets you inspect the Apollo Client Devtools extension. If you do this, do you see errors in the JavaScript console there by chance? |
im seeing these: |
How strange! I've never seen that kind of error. We don't have a |
i just have quilbot and apollo |
im not sure but this might be the problem: |
Perhaps? Can you try opening the explorer in its own tab? I'd be curious if this is loading for you: https://explorer.embed.apollographql.com/ |
Interesting! Would you mind opening a support ticket using the link in that screenshot? Unfortunately I'm not on the team that owns this codebase since its an iframe into our embedded explorer. I'll raise the issue internally with the team as well. |
i deleted my last comment because it worked again (the link) |
I will |
in the end i have a question: it should help me to fix this maybe |
It looks like it will be disabled if its unable to setup the iframe for the embedded explorer: apollo-client-devtools/src/application/components/Queries/RunInExplorerButton.tsx Line 26 in 5a75c41
This is set from the Explorer tab in
which itself is called if we are able to get a message from the underlying iframe: apollo-client-devtools/src/application/components/Explorer/Explorer.tsx Lines 155 to 162 in 5a75c41
My guess is that since your machine is unable to setup the iframe, it can't receive the message, so the button remains disabled. |
That is very very helpful |
If it would help to run the extension locally so you can add logging to the code, check out the instructions from this comment: #1396 (comment) (I really gotta move these to the README 🙃) |
I made an iframe in my project with the url you provided and i got this: |
Can you use the full URL that we do in the devtools to check to see if this is still the case? In the extension, we route the network requests through your actual Apollo Client instance connected to devtools, so the fetch happens in the top frame. Here is the URL: apollo-client-devtools/src/application/components/Explorer/Explorer.tsx Lines 270 to 271 in 5a75c41
where That |
I tried it again with the full url as you said, and this was the result : Access to fetch at 'https://studio-ui-deployments.apollographql.com/build/iframeIdentitySync.html' from origin 'https://explorer.embed.apollographql.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
|
and here is my test code for the iframe:
|
I found the problem my DNS server was the problem and the sync of the iframe was interrupted by it I just used a vpn and every thing is working |
Unfortunately I have no way to reproduce this, so at this point I'm not even sure how to begin figuring this out. It's odd to me that you're seeing different error messages from the devtools errors and the raw iframe you're using here. If you're willing to help out and dive in a bit deeper since you're able to reproduce it on your machine, that would be greatly appreciated. Clone this repo and use the steps outlined in #1396 (comment) in order to run the extension locally. Perhaps having access to the raw code can help get a bit closer to the issue. |
Oh awesome! Seems I posted my comment too soon 😆. Thats fantastic! |
I'm so sorry about it |
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better. |
No problem! I'm just glad you were able to figure it out. At least this leaves a paper trail for anyone else that may stumble into the same issue. Have a great rest of your day! |
I have devtool on my other device and it work flawlessly but in my new device everything is working except Explorer and its blanked out
@apollo/client
version3.8.8
Apollo Client Devtools version
4.18.6
The text was updated successfully, but these errors were encountered: