This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (3)
- # boot (2)
- # cljs-dev (11)
- # cljsrn (122)
- # clojars (9)
- # clojure (8)
- # clojure-austin (5)
- # clojure-korea (1)
- # clojure-russia (3)
- # clojure-spec (7)
- # clojure-uk (14)
- # clojurescript (45)
- # cursive (12)
- # emacs (7)
- # euroclojure (1)
- # hoplon (285)
- # instaparse (1)
- # klipse (37)
- # leiningen (1)
- # off-topic (3)
- # om (11)
- # onyx (4)
- # re-frame (5)
- # reagent (1)
- # sql (3)
- # uncomplicate (2)
- # untangled (17)
- # vim (5)
@keithsparkjoy I think I was actually getting that earlier too when I was trying to make a new app out of the blue. I forget if it was that exact error, if I was able to fix it, or if it was just something that I messed up in XCode or a syntax bug so the thing couldn’t compile. Sorry that wasn’t very helpful. 😕
Yo, who wants to help make an Android clone of Whale with Om Next? 🙉😋
P.S. I have no idea wtf I’m doing:)
@keithsparkjoy I think the actual error is not in the snippet you posted
this looks like an XCode problem. my suggestion would be to try this:
rm -rf "$HOME/Library/Developer/Xcode/DerivedData"
otherwise try opening the project in XCode and run it from there
maybe it'll give you better information
Thanks @pesterhazy - will give that a shot.
Hmm, doesn’t seem to be a DerivedData subdir under my $HOME/Library/Developer/Xcode
Maybe I should try completely uninstalling and reinstalling XCode wholesale.
what version is your xcode?
ah. I'm still on 7.3
what error causes that compile to fail? It should be further up in the terminal output
btw it could be this: https://github.com/facebook/react-native/issues/8584#issuecomment-236366222
or update to react-native 0.33 in package.json
I’m going back and running react-native run-ios, which is what produced that error.
scrolling up through all the output
Yep, looks like it’s the same issue you posted above
yeah apple decided to upgrade a warning to an error in xcode 8
Maybe I should try Xcode 7.3
potentially updating rn just fixes things
I'd try that first
okay will look for package.json
found it in example/app
that's the one
currently says "react-native": "0.30.0"
gonna switch that to 0.33.0
then npm install I suppose
sorry I’m such a newb at all of this
Okay npm install gave me a warning: UNMET PEER DEPENDENCY [email protected]
ah you have to update that one as well
ahh another update to package.json is needed
So there’s react and react-dom - gonna update both of those in package.json to 15.3.1 and see if that does any better
okay happy npm now
ooh this is looking better now
woohoo! Build succeeded!
nice. if all works, I'll update BRN's example app
the IOS app did come up, although it’s quite red
goog.require could not find: cljs.core
so not quite there yet.
ahh gotta apply the patch
boot dev should do that automatically these days
yep that patched it. Trying again.
boot dev is running, then ran react-native run-ios and still red. This time, Could not connect to development server. It’s asking me to run ‘npm start’ - I don’t remember seeing anything about that in the getting started doc...
either npm start, or “ensure… Node server URL is correctly set in AppDelegate"
Not seeing that in the troubleshooting guide - will google around
Found this, “Run npm start on local machine to start the development server. React Native relies on a development server to communicate with the app running in the simulator."
I wonder if there’s a step missing in that getting started blog post
I was thinking ‘boot dev’ was the development environment.
So there must just be something broken still - somehow I think running 'npm start’ doesn’t make sense here.
npm start runs the RN packager
that used to be part of BRN, but that turned out not to work too well
nowadays we just ask users to run
npm start in a terminal
usually the packager starts itself in a new window when you do run-ios, but obviously that doesn't work always
I should add that to the guide
the packager did start I think
let me try again..
ah then it's a good idea to close that window and start
npm start manually
from what directory?
example? or example/app
i.e. the directory that contains package.json
okay so first
cool okay trying again
you'll see the packager working after run-ios
sometimes that takes longer than 60s the first time, and you get a red screen
do not give up!
just reload it again in the simulator
kinda sitting there now, I’m waiting
okay red again...
yea same message
did the packager complete?
still at 794/795
if that’s what you mean
yeah, that means it's not finished
It did say <END>
you can try getting that url in a browser
see if you get a bundle
It takes 2-3 seconds to return it, but yea, looks like that URL is alive.
so try reloading in the sim again now
well dang there it goes
Welcome to boot-react-native
Button works. Woohoo!
Thanks for your patience, @pesterhazy
it should be faster now, with the packager's warm cache
Now to explore native development with cljs. Fun fun fun 🙂
Pretty amazing to be able to change the text of that button, but see the state stay the same. Magical.
yeah that's the idea, and hugely helpful when building apps
it works well for us for a moderately sized app (Fy, in the iOS app store if you're curious)
@keithsparkjoy if you could put up a github issue with the problems you encountered with the guide, that'd be amazing: https://github.com/mjmeintjes/boot-react-native/issues
Sure I can do that.
number of screens 🙂
I started from scratch and ran through it again to make sure it all worked as advertised. Got it working again.
awesome, thanks. That's great for googl-ability too 🙂
@keithsparkjoy updated the example app in master to use rn 0.36, seems to work fine