Has anyone ever seen this error while using app host on local host on macOS?
The webpage at *<http://localhost:3000/plasmic-host#origin=https%3A%2F%2Fstudio.plasmic.app&isProd=true&appConfigOverrides=&studioHash=9e3b4c>* might be temporarily down or it may have moved permanently to a new web address.
Works on my linux and windows machines but can’t seem to run it from my macbook. Tried both a fresh plasmic repo and private browser with no luck.
/plasmic-host returns expected page
oddly enough it doesnt work with gitpod piped through localhost… sounds like a firewall thing maybe but my firewall is definitely turned off.
Do you see any errors from the console tab in the Chrome developer tools?
just a couple warnings
main.c62aa8db.js:33 Rendering app
main.c62aa8db.js:33 Hello, Uri
main.c62aa8db.js:33 Rendering app
25.22647a55.chunk.js:1 Drift: Identity Successfully Updated
25.22647a55.chunk.js:1 DRIFT_WIDGET:: widget_core:bootstrap_api finished in 113 ms
main.c62aa8db.js:33 A soft navigation has been detected: <https://studio.plasmic.app/projects/xexhaNPkVpnMwPrLrpJbfo>
main.c62aa8db.js:33 [PlasmicWindow] Listening for PLASMIC_HOST_REGISTERED message
3DevTools failed to load source map: Could not load content for <chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/browser-polyfill.js.map>: System error: net::ERR_FILE_NOT_FOUND
DevTools failed to load source map: Could not load content for <chrome-extension://ojnikmlgjpfiogeijjkpeakbedjhjcch/toggle_icon.js.map>: System error: net::ERR_BLOCKED_BY_CLIENT
DevTools failed to load source map: Could not load content for <chrome-extension://ojnikmlgjpfiogeijjkpeakbedjhjcch/toast_iframe.js.map>: System error: net::ERR_BLOCKED_BY_CLIENT
DevTools failed to load source map: Could not load content for <https://studio.plasmic.app/static/js/6907.f6fc9475.chunk.js.map>: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for <https://studio.plasmic.app/static/js/main.c62aa8db.js.map>: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for <https://studio.plasmic.app/static/js/4790.f74ee3ec.chunk.js.map>: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for <https://studio.plasmic.app/static/css/base.css.map>: Unexpected token '<', "<!doctype "... is not valid JSON
(index):6736 crbug/1173575, non-JS module files deprecated.
(anonymous) @ (index):6736
60[Violation] 'setTimeout' handler took <N>ms
Are you able to try from a brand new Chrome profile?
I did just notice this in the node console. not sure if relevant
demo:dev: <w> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Resolving 'next/dist/build/webpack/loaders/next-flight-client-entry-loader' in /Users/kylekitlinski/_dev/final-dutchman/apps/demosite/node_modules/next/dist/compiled/loader-runner for build dependencies doesn't lead to expected result '/Users/kylekitlinski/_dev/final-dutchman/node_modules/next/dist/build/webpack/loaders/next-flight-client-entry-loader.js', but to '/Users/kylekitlinski/_dev/final-dutchman/apps/demosite/node_modules/next/dist/build/webpack/loaders/next-flight-client-entry-loader.js' instead. Resolving dependencies are ignored for this path.
demo:dev: <w> at unknown 4 next/dist/build/webpack/loaders/next-flight-client-entry-loader
Am I still the only one who’s had this issue? Curious if anyone else is running mac 13.2+ and not having issues? I have no idea why that would be it but its the only thing I can think of
I’m wondering if the plasmic-host url you’re using is correct… the part after the hash is normally what plasmic studio appends to the url when its embeds it in the iframes. you just need http://localhost:3000/plasmic-host , nothing more
@stuck_guineafowl Thanks for the reply it is the same result without the querystring at the end I’m not sure why I copied it like that when I took the screenshot
i had an issue at some point that was preventing plasmic studio from working:
https (plasmic) to http (app host)
try running the app host on https
That sounds like it might work actually based on symptoms I’ll give it a shot and report back