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.

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)

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

@jeaye annoying I know

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

that's for iOS though

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

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

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

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

Damn, broke fighweel again by upgrading to 0.50.4.

@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

Seems like only the right amount of atonement will.

Sometimes atonement is what it takes