Fork me on GitHub
#cljsrn
<
2017-12-21
>
jeaye03:12:41

I've just upgraded to RN 0.49.0 and now it seems I'm unable to connect to figwheel; the app runs fine, from react-native run-android, butI see Figwheel: trying to open cljs reload socket in the log every several seconds.

jeaye03:12:57

Has anyone else run into this? (I was on 0.47.0, which worked fine, then went to 0.48.4, then to 0.49.0)

jeaye05:12:00

Meh. Lots of uninstalling, reinstalling the app, cleaning things, etc did the trick. The diff is clean, but figwheel works now.

pesterhazy12:12:06

@jeaye annoying I know

pesterhazy12:12:02

for reference, I use something like this script to nuke the env: https://gist.github.com/pesterhazy/7fc7e020afa040bef6b11f06b62d2821

pesterhazy12:12:34

that's for iOS though

jeaye17:12:51

@pesterhazy Thanks. Looks like it'll be simple for me to port it to Android.

jeaye19:12:19

@pesterhazy You can add those dirs you're rming to :clean-targets in your project.clj.

jeaye19:12:36

i.e. :clean-targets ["target/" "ios/build/" "index.ios.js" "index.android.js"]

jeaye19:12:11

Looks like lein will clean the DerivedData for you, too, if you allow it to reach outside the repo: https://github.com/technomancy/leiningen/blob/stable/sample.project.clj#L329

jeaye19:12:07

Damn, broke fighweel again by upgrading to 0.50.4.

jeaye19:12:39

@pesterhazy I scrub even more thoroughly than you, but it doesn't fix this Figwheel: trying to open cljs reload socket issue. https://gist.github.com/jeaye/3669b2d1a5f5396684e7ebb34458a94c

jeaye19:12:48

Seems like only the right amount of atonement will.

pesterhazy22:12:21

Sometimes atonement is what it takes