This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-23
Channels
- # admin-announcements (38)
- # announcements (1)
- # aws (1)
- # beginners (195)
- # boot (1)
- # business (3)
- # cider (100)
- # cljsrn (37)
- # clojure (99)
- # clojure-russia (69)
- # clojure-switzerland (1)
- # clojurescript (120)
- # datavis (26)
- # datomic (23)
- # devcards (4)
- # editors (38)
- # hoplon (18)
- # ldnclj (27)
- # lein-figwheel (28)
- # off-topic (50)
- # om (329)
- # onyx (255)
- # portland-or (1)
- # re-frame (8)
- # reagent (18)
- # spacemacs (5)
- # testing (1)
@chadhs: You rock, thanks!
in case someone has an issue with:
$ natal init myapp
Creating myapp
Creating Leiningen project
Updating Leiningen project
Creating React Native skeleton
Installing Pod dependencies
Updating Xcode project
Creating Natal config
Compiling ClojureScript
Compiling Xcode project
Command failed: xcodebuild -workspace native/ios/wios.xcworkspace -scheme myapp -destination platform='iOS Simulator',OS=latest,id='481413B2-9E0A-4EFB-83E8-2F118ECE4046' test
– make sure you nmp install react-native-cli
first, as it does not get installed for you by natal
.
related: https://github.com/facebook/react-native/issues/3948If it does, probably appropriate to file an issue with Natal—it tries very hard to ensure all required deps are present and at their minimum required versions or better
I did not have any node/npm on my machine before I tried natal few months back. today I came back to it, ran through all the dependencies installations again. And eventually got stuck with this error. I'd consider this as almost clean install.
I am pretty disoriented in all the dependency/responsibility graph so far, and chose to comment on react-native issue above + spill it out here "informally" first.
not sure if xcode and other versions matter, except natal's one:
$ natal --version
0.1.11
There's an over-abundance of stuff to get right when trying out React Native from ClojureScript—Natal has done a great job of making it easier to try (especially if you're very busy and don't have the time to invest in the half-dozen things you got to get right)
@misha - I seem to recall (been a while) I got a similar message and had not gotten through the xcode licensing issue - worth checking.
there was another, xcode-related issue. natal picks uses iphone6(+?) as a default simulator device. I had xcode 6.# updated in august, which did not have that simulator. So I got this error https://github.com/dmotz/natal/blob/master/natal.coffee#L72
logErr "Cannot find device `#{deviceName}`"
on Creating Natal config
step@misha: Da, I'm able to reproduce what you're seeing. Perhaps Dan Motzenbecker didn't intend for there to be such a dep. Worth filing an issue against Natal
@donmullen: true, accepting xcode's terms was one of the steps of my journey today, but it said it explicitly somewhere.
@dmotz Yes, and the use of natal-shell
and illustrating how to make a button are useful. This is getting really really good for a first-run experience!
hi, @dmotz today I upgraded natal from 0.1.7 to 0.1.11. Do I need to upgrade the projects I started on 0.1.7? If so, how do I do that? Thanks! 😄
@felipebueno: no need to upgrade anything in the project. you should get the new compiler feedback in the REPL now when you run natal repl
nice thanks
oh I didn't know that... but I'm using Emacs + Cider so there's no need for that 😄
yep. I'm one of the guys bothering you on the cider issue on github hahah
that'd be great. It could be something that works with Cider, Cursive, LightTable etc right out of the box
Some interesting articles in this react native newsletter : http://brentvatne.ca/react-native-newsletter/22-11-2015.html