I suspect that you have shadow-cljs running twice in the project

they basically interfere with each other and overwrite each others files

I think you’re right.

make sure to kill them all and start a clean one

No dice. I deleted my .shadow-cljs, and my build files, launched my native build and I’m getting the same error. Did I miss the point?

yes. deleting the files is exactly what will get you into this mess

the .shadow-cljs files keep references to the running process

so by deleting them you remove any trace of something that may still be running

basically never ever do that, there is never a good reason to

what you need to do is kill the running java processes

Oh, we are definitely talking about 2 different things

or if you can still access it open a REPL and type (System/exit 0)

but that won't work if there is a zombie process which you can't connect to anymore because you deleted the files

when in doubt just reboot 😛

just make sure there is no running java process in that project directory

so I killed all java processes, started my shadow watch, ran my expo development build and I’m getting the no connection error.

ok, now that we are in a clean state we can investigate further 😛

what is expo trying to connect to?

This was expected behavior for me. My wires were crossed, because I often build my browser and native builds at the same time through a npm run script.

I’ve done both the go app and a dev build, ios and android simulator. ATM it’s a dev build on ios

you can do that via shadow-cljs watch native node, it should not be 2 separate shadow-cljs commands in case you are doing that

> what is expo trying to connect to?

does it give you any indication what host it tried to connect to? an ip or something?

> I’m getting the no connection error.

so not the "build not running" error?

It does not. I’ve given you all the errors I’m getting. It’s surprisingly thin, just a singular log line and the stack on the simulator

I get “sahdow-cljs watch for build :native not running!”

just to confirm

..

ok please take a second

and be extra clear about what errors you are getting

> “sahdow-cljs watch for build :native not running!”

means that the connection worked just fine

yes

since otherwise it wouldn't know that the build is not running

> shadow-cljs - remote-error {"isTrusted": false …}

I follow you

this is the "no connection error"

they are two very different things with very different causes, so please be clear

I get that error when I expect to, i.e. after I C-c my build.

sorry I have an extremely hard time following you

lets start from the beginning

I’m sorry. I’m not the most graceful online. I’m not trying to be bad at this.

you start npx shadow-cljs watch native?

what does that log give you

please just paste the entire log

I want to get away from me guessing what is happening 😛

› Installing on iPhone SE (3rd generation) › Opening on iPhone SE (3rd generation) (net.drilling) › Opening on iPhone SE (3rd generation) › Opening the iOS simulator, this might take a moment. › Logs for your project will appear below. Press Ctrl+C to exit. iOS Bundled 4255ms (index.js) LOG debug LOG start LOG shadow-cljs #3 ready! ERROR shadow-cljs watch for build :native not running!

that is not the log I asked for

What log?

I literally want you to run npx shadow-cljs watch native and give me that log

➜ shadow-cljs watch app/native shadow-cljs - config: /Users/pat/fjck/shadow-cljs.edn shadow-cljs - socket connect failed, server process dead? shadow-cljs - starting via “clojure” shadow-cljs - HTTP server available at http://localhost:5308 shadow-cljs - HTTP server available at http://localhost:5309 shadow-cljs - server version: 2.27.4 running at http://localhost:9630 shadow-cljs - nREPL server started on port 5310 shadow-cljs - watching build :app/native [:app/native] Configuring build. [:app/native] Compiling ... SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [:app/native] Build completed. (182 files, 0 compiled, 0 warnings, 3.66s)

I don't care about expo yet

ok good

open http://localhost:9630/builds

Am I supposed to report back something specific?

you should see your builds, with native running (aka green dot)

Yes

ok, just checking

so now if you start expo

start and leave it running, no ctrl+c anything please. both processes.

It’s loaded with the shadow error in question in a popup on the bottom.

which shadow error

build not running?

yes sir

open http://localhost:9630/runtimes

how many items are listed?

should have #1 JVM Clojure, and then more?

2, I’ve got “#1 JVM Clojure” and “#5 - build: native”

so it connected just fine

and if you click back to builds the native build is definitely still running?

wait

about you had shadow-cljs watch app/native ?

I did.

what is the actual build id? namespaced keywords are not allowed there

app/native

so there is a :builds {:app/native {:target ...}} config in shadow-cljs.edn?

yes sir

well .. that is obviously not :native, so no wonder it cannot find it

make that :app-native or just :native and you should be fine

build ids should not be namespaced keywords

Oooof, It didn’t cause issues for tests or the browser version.

man, I feel I should know that.

I don't have an immediate guess why its a problem in expo, but I mean now that we found it its pretty obvious 😛

Well, I really enjoy your tool. It doesn’t give me issues like this. Most everyday it just helps me work. So thanks for this and shadow.

CONFIRMED: namespaced build id caused hot reload to break in expo. Thanks @U05224H0W

https://github.com/thheller/shadow-cljs/issues/1172

should at the very least give the correct error 😛