@mdhaney Thank you so much!😊 Your experience makes me a lot less detours. Do you use “re-natal init ProjectName -i om-next” for scaffold? My workflow is using : expo init ProjectName(it’s “expo”: “^31.0.2”),then add the shadow-cljs.edn. then yarn add ntl-messageformat@^2.2.0 ,then add wilerlucio’s glue code. compile the cljs to node_modules/xxx ,then import to the App.js.

If @mdhaney or @eric.shao or anyone wants to contribute a “native appendix” for the book, I’d gladly include it.

@tony.kay I would be happy to do that.

@tony.kay I’d like to but not capable of that,I wish I can. I will follow along,report my issues.

Hi! I added a test to the template (sample_spec), like this: https://gist.github.com/hmaurer/13455db916c5790ed81a59bd883a3df8 However, only one test is showing up in the UI: https://puu.sh/CpgCL/7dc29176f3.png What did I do wrong?

surely I can have more than one specification in a file, right?

@hmaurer Make sure your dev console is open and look for errors.

of course you can put any number of specs in a file

they are just deftest with some extra rendering events

Make sure you’re on the right http port as well. Hm, actually that shouldn’t matter…I was thinking hot code reload was hosed perhaps.

Also make sure the test build is active

@tony.kay I don’t seem to have any errors in the console (I checked that before sending the screenshot), http port seems right, and I am running the test build, i.e. shadow-cljs watch cards test