Thanks! Yeah, I saw that—but when I run (shadow/repl :browser) or (shadow/repl :react-native) I get a :no-worker error … whether from Cider or the command line

Have you done shadow-cljs cljs-repl app?

Here’s what I’ve done: shadow-cljs watch app in one terminal (starts build and reports nREPL server started on <port>) yarn start in another (starts Metro) yarn ios in another (builds and runs XCode project) After that, I can connect to the hosted nREPL via M-x cider-connect without issues, but I can’t boost that to a CLJS repl using (shadow/repl) If I run shadow-cljs cljs-repl app in another terminal, I get a REPL prompt but trying to interact with the JavaScript runtime (eg via a (require '["react-native" :as RN])) fails telling me no application is connected

Apologies for the long message. I’m wondering if there’s something about the way I’m launching the app on the iOS simulator that’s leaving out the entry point for the CLJS REPL connection?

@attentive the commands look correct altough REPL require likely won't work like that since react-native doesn't really support loading dependencies at runtime

I'm planning to do a cleanup pass over the code to allow at least requiring things that had been required before

one issue I still need to solve is the proper detection of the host ip

if it detects the wrong IP the native app will fail to connect to the websocket endpoint required for the REPL to work

so if you don't see a WebSocket connected! console message on startup that is likely the problem

Can I manually override that IP?

you can set :local-ip in the build config currently I think

it should be printing Using IP: ... on watch start

Interesting! Yes it’s not doing that. Here’s the messages I see:

shadow-cljs - config: /Users/tom/dev/scout/shadow-cljs.edn  cli version: 2.8.24  node: v11.12.0
shadow-cljs - server version: 2.8.24 running at 
shadow-cljs - nREPL server started on port 52514
shadow-cljs - watching build :app
[:app] Configuring build.
[:app] Compiling ...
[:app] Build completed. (231 files, 18 compiled, 0 warnings, 5.67s)

So I’ve been able to M-x cider-connect to the reported nREPL port 52514, but nothing beyond that

oh try shadow-cljs watch app --verbose. it might not have the correct log level

Okay got it Using IP: 192.168.1.120 … I’ll try adding this to :local-ip

Thanks a lot for your assistance on this. I’ll push these changes into my de-Expo’d fork of rn-rf-shadow if it all starts to work nicely, and take a look at your doco

that looks like its using the correct ip? or is that not the correct one?

Yeah it does seem to be, so guess that was a red herring (that is my LAN IP currently)

yeah it sometimes picks other ips if you have docker or other virtual container stuff running so that leads to issues. The yarn start output should be logging the websocket connected message when you open the app?

I just start things and connect the cljs-repl. No hassles. So, when you have run yarn ios, you have the app running in a simulator, or your physical device and still can't evaluate stuff from the shadow-cljs cljs-repl app prompt?

This may be the issue: when I run yarn start it doesn’t actually run the app, it just runs the bundler

yes I know

When I run yarn ios the app runs in the simulator but I can’t connect beyond that

but the bundler typically shows the console.log messages from the running app

Not in my case!

Perhaps that’s indicative of the problem (networking for the simulator?)

really? I thought metro always did that?

It’s just showing the BUNDLE / DELTA messages at the moment

might be a expo only thing then

maybe the react-native log command shows it?

or whatever the command was. there was something to get the console.log messages of the compiled code

I can get it using xcrun mojo but it doesn’t appear to show the Websocket Connected! message I would expect

Yeah it’s react-native log-ios in this instance

and it doesn't log anything?

Nothing useful. I get the application messages from another command fine, but I don't see the websocket initialisation message. That may be because of other factors though so bear with me!

I get the Websocket Connected! message in the expo start output. Don't you get that, @attentive?

I've removed expo from the project ... I've got a port of rn-rf-shadow off expo I'll have another poke at a little later tonight (I'm at GMT+0930 so just having dinner!)

Just to come back to this issue … the REPL networking is now working correctly as far as I can determine (REPL connects from the command line). I think it might have been errors during initialisation that were causing issues before

I can require local dependencies such as (require '[re-frame.core :as rf :refer [dispatch subscribe]]) etc so I feel like I’ve got what I need

Still having a few issues connecting from CIDER. cider-connect seems to set up a CLJ REPL (which connects correctly) and then I can’t switch to the REPL window?

see https://shadow-cljs.github.io/docs/UsersGuide.html#cider I think you need cider-connect-sibling-cljs