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

Can't get to work with localhost #8

Open
Cipher-Coder opened this issue Nov 23, 2019 · 8 comments
Open

Can't get to work with localhost #8

Cipher-Coder opened this issue Nov 23, 2019 · 8 comments

Comments

@Cipher-Coder
Copy link

I am developing locally and attempting to use your extension while my site is running on localhost and all I get are blank windows. I have enabled the setting to use local files and that is good for pulling up /home/websites/testingSite/index.html however I am using Gatsby on this project, running a local server with http://localhost:8000 and I am unable to load it.

@skmail
Copy link
Owner

skmail commented Nov 23, 2019

are there any errors in the console?

@Cipher-Coder
Copy link
Author

responsiveViewer

I have enlarged the console so you can see it. - No errors though.

@Cipher-Coder
Copy link
Author

So if I try to refresh the page I actually get something....

responsiveViewerError

@Cipher-Coder
Copy link
Author

I am using Windows 10. Developing with Gatsby. I use VS code and Chrome Canary. Although I tried it on regular Chrome too and it would not work. Same results. -Sorry I did not put this in my original issue- I also tried this on Linux Mint and I am getting the same behavior using regular Chrome.

@skmail
Copy link
Owner

skmail commented Nov 24, 2019

can you pull the source code and build the extension? there's a bunch of fixes on the networking side of the extension, meanwhile, I will check the extension on gatsby projects.

@Cipher-Coder
Copy link
Author

Ok... I cloned the repo => installed dependencies => ran npm build => I installed the build as an unpacked extension in Chrome on Windows 10 as well as Linux Mint. Still no luck. I really like the extension so I went a bit further...
I tried to look at it with gatsby develop as well as gatsby develop -H 0.0.0.0 -p 8000 with no luck on either.
However... The only good luck I can report, is that this looks like something with Gatsby. When I ran a Svelte/Sapper project in dev mode on localhost:3000 with the Sapper framework.. It worked perfect. It appears that this is specific to Gatsby.

@Cipher-Coder
Copy link
Author

I found a workaround..
The only way I can get content to render in the iframes and not just be blank, is after the initial load, go to the screen selection tab and deselect then re-select one of the screens. Does not matter which one. After that it triggers all the screens to re-render... then it loads on all of the screens still selected.
Still not sure why this is happening with Gatsby projects, but at least I am able to use the extension for now.
I am not sure if this will help you at all... but if anyone else is working with Gatsby and has this problem, at least it will work. Just a matter of hitting a button twice once it is loaded.

@chrillewoodz
Copy link

I can confirm that the workaround is working, however it's very annoying :(

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

3 participants