thats fine too

(since i’m testing on a device)

it says “websocket not connected”

I mean you literally open that url in a browser on the device

same with Safari on Mac, though (where reload works)

see what the browser has to say about that

yes, the browser displays a page with the above text

oh right ... guess the websocket connection is failing there too

yeah nevermind it doesn't expect ssl yet

but the connection itself works? no warnings or so?

Looking in the inspector, it says “[blocked] The page at https://dolly.local:9630/dashboard was not allowed to run insecure content from <ws://dolly.local:9630/api/ws>. p1 — app.js:1877:84”

(my computer’s name being dolly :-)

yeah that is the UI websocket. unrelated to a build ws

not sure why it would fail your websocket

it should be connecting to ...

seems to do so in Mac Safari … I’ve probably still not installed the cert correctly on the iPhone

self signed ssl certs suck 😞

There’s a post here from jan 18 that also mentions not being able to use wss on iOS with self-signed certs, even though it works on Mac: https://stackoverflow.com/a/48155102/202538

He suggests not using SSL, but the problem is, I’m playing around with the getUserMedia api that requires it. I guess I’ll just have to live without hot-reloading on the iOS device. It still works perfectly on both Android and Mac Safari though.

Hey all, been using shadow-cljs for a few months now and finally getting productive. I ran into an issue today that I’m just not able to debug and was hoping someone here may have seen the same thing and has a resolution. I have a situation where “nested” Reagent components won’t cause a re-render in the browser if I save the file the function returning the renderer is defined in. However, if I change the calling file things get picked up just fine. Moving the nested function into the same file as the caller will also result in a success, so it doesn’t appear I’ve got the return value wrong. In both cases the shadow-cljs loader icon will pop up and in the browser as if things worked. Any ideas?

if you keep a function reference to something from another namespace that function reference can't be updated

(def x other-namespace/foo)

if you update the code in the other-namespace x won't be updated (only if the namespace with x is also reloaded)

I’ll move things into a gist so it’s more clear

@thheller here’s a clearer explanation I hope. If I updated the contents of login-panel/component, let’s say change the text of “Sign In” to “Other Sign In”, things won’t reload even though the spinner appears. Apologies if this is exactly what you’re explaining and I just don’t understand quite yet 😉 https://gist.github.com/reset/cc0781ec1cf45dc20f7238a98eaf0030

@jamie857 are you re-rendering the application?

Added the r/render call as well to that gist just now

I don't know much about reagent but it may just short circuit your render somewhere. just stop rendering because it thinks nothing changed

@lilactown I’m not sure, but what I am doing is modifying the function, saving the file, and not seeing the page automatically reload

do you have the hooks configured correctly? because the gist is not correct

Which portions are incorrect? I’m lifting this out of an app and trying to form it for the gist, so I might have things wrong

And which hooks?

I believe you need to set :dev/after-load for your start! function

for one you should never call (start!) like that

https://shadow-cljs.github.io/docs/UsersGuide.html#_lifecycle_hooks

Perfect

I’ll look into these bits

you should also get a warning on the console if no hooks are configured

I see that now, yep. No after-load hooks are configured

yeah then your render is simply not triggered

(defn ^:dev/after-load start! [] ...)

Giving this a shot now

This will take me a bit to digest and try out but thank you very much for the help. I’m going to re-read the docs and see what I end up with. And thanks for shadow-cljs, even though my setup is clearly not there it’s been a pleasure to iterate with