Fork me on GitHub
#cljsrn
<
2016-08-22
>
pesterhazy10:08:15

RN packager: transformed 932/933 (100%)[12:20:25 PM] <END> find dependencies (407404ms)

pesterhazy10:08:26

jesus, 6 minutes for initial transform

artemyarulin11:08:38

О_О how big is your app?

pesterhazy12:08:43

it's not that big

pesterhazy12:08:04

I tried updating node to 6.4 in hopes that it'll help

vikeri12:08:05

Any idea why boot-reload does not work for me on Android? I am monitoring the traffic in Android Studio but I’m unsure if it detects web sockets.

pesterhazy12:08:31

how do you start the app? on device or in the simulator?

vikeri13:08:52

Can’t get the REPL to work either… Something fishy going on here.

pesterhazy13:08:08

you did the whole adb reverse dance?

boorad13:08:29

I can’t get REPL to work either, ios only so far

vikeri13:08:10

@pesterhazy: Yes I did, curiously enough I don’t get that error. So maybe the connection is working?

pesterhazy13:08:54

I think it should say "reload socket connected" in your device log

vikeri13:08:58

Do not get that, but I get these errors though E/ReactNativeJNI: Unable to load script from file and E/Surface: getSlotFromBufferLocked: unknown buffer: 0x9f44fdc0

pesterhazy13:08:56

did you disable live reload and hot reload in the app menu? (you should)

vikeri13:08:23

Yes, they are disabled

pesterhazy13:08:54

hm. it works for me, I just checked

pesterhazy13:08:08

on an android device on 0.3-rc1

vikeri13:08:08

Yeah I checked it in the example, there it worked fine.

vikeri13:08:53

Could my newer Cljs/clj versions mess things up?

pesterhazy13:08:57

is your build.boot similar to the one from SimpleExampleApp?

pesterhazy13:08:02

I wouldn't rule it out

pesterhazy13:08:21

you don't see anything in the logs?

pesterhazy13:08:58

I get this: I/ReactNativeJS( 2553): Reload websocket connected.

vikeri13:08:11

I don’t see that

vikeri13:08:21

There are some issues here and there, but the most suspicious are the ones I wrote further up

pesterhazy13:08:45

I've no idea what these mean

pesterhazy13:08:53

when did you generate your android project?

vikeri13:08:00

Do you mean react-native upgrade or react-native init?

vikeri14:08:36

Waaay back, before 0.30 for sure.

pesterhazy14:08:38

I think there were some things in latest updates that you need to do manually

pesterhazy14:08:53

though that's a shot in the dark

pesterhazy14:08:02

check the release notes for each release

vikeri14:08:16

For RN or brn?

pesterhazy14:08:22

react-native

pesterhazy14:08:32

although not sure how that would affect it

pesterhazy14:08:49

maybe it's how you integrate boot-reload

pesterhazy14:08:10

boot-reload injects itself into main.cljs.edn - maybe that part goes wrong?

vikeri14:08:43

adzerk.boot-reload.init1234 is required and run. But I’m not sure about the rest of the namespaces.

pesterhazy14:08:25

hmm, that seems sufficient

pesterhazy14:08:35

maybe add logging to boot-reload to see what goes wrong?

vikeri14:08:01

Like verbose? Or manually go in and add console.log statements?

vikeri14:08:15

Couldn’t find a verbose flag.

pesterhazy14:08:44

I'd manually go in and add console.log's

pesterhazy14:08:55

a bit annoying, especially given the long feedback cycles

vikeri14:08:28

Well, having done that, the issue is that the websocket never seems to connect.

pesterhazy14:08:42

very annoying

pesterhazy14:08:02

you could try to access the websocket url through a browser on the device

pesterhazy14:08:09

to see if the network connection even works

pesterhazy14:08:20

websocket sort of sits on top of http

vikeri14:08:25

I get, websocket connection only. So it seems to work...

vikeri15:08:33

@pesterhazy: Hours later: Error triangulated! RN 0.31 was the issue, it works in 0.30 but not in 0.31. :thinking_face:

pesterhazy15:08:04

could you add a GH issue?

vikeri15:08:34

Well, I see that as well in 0.30 but not in 0.31. So possibly the fix broke it

pesterhazy15:08:49

that's what I was thinking