Fork me on GitHub
#cljsrn
<
2016-06-16
>
rastandy08:06:46

is there someone who can run this clojurescript code in react native without having a EOF exception?

vikeri12:06:22

@rastandy: I did and it spat out the feed in the console.

pesterhazy13:06:54

@rastandy: which react-native version and platform is that?

rastandy13:06:56

from package.json:

rastandy13:06:58

"react": "^0.14.8", "react-native": "0.24.1",

rastandy13:06:37

I had the same problem yesterday with

pesterhazy13:06:45

I remember hearing that fetch on android gives trouble but is fixed in 0.27.2

pesterhazy13:06:54

might be worth upgrading?

rastandy13:06:08

i tried yesterday to upgrade to 0.27.2

rastandy13:06:14

with partial success

rastandy13:06:22

but I had the same problem

rastandy13:06:32

@vikeri thanks for trying it out

rastandy13:06:01

@vikery on which version did you ran it?

savelichalex13:06:12

@rastandy: just create new project from scratch with newest RN and try

vikeri13:06:29

"react": "15.1.0","react-native": "0.27.0",

rastandy13:06:32

yeah you are right I’ll do that from scratch

rastandy13:06:28

thank you guys, you are always helpful!

rastandy13:06:34

I have problems running a brand new project with re-natal

rastandy13:06:39

at least with android

rastandy13:06:32

my command was: re-natal init MyApp -i om-next

rastandy14:06:05

the app won’t run unless I enable the “Debug JS Remotely” option

vikeri14:06:24

Have you tried it with ios?

rastandy14:06:36

I’ll try it

rastandy14:06:35

but lein figwheel ios still wait for connection

rastandy14:06:07

but the sample app starts and works

rastandy14:06:37

no I can’t believe that

rastandy14:06:01

my figwheel from the old re-natal project was still running

vikeri14:06:04

You’ll have to enable remote debugging on it as well

rastandy14:06:04

with ios everything works, also the fetching my feed with js/fetch

rastandy14:06:04

In android I have problems running the app, I’ll try to start it without figwheel

rastandy14:06:20

when running the production version (whitout figwheel) the app runs

rastandy14:06:35

but I have problems fetching the feed

rastandy14:06:44

same error: Unexpected EOF

vikeri14:06:45

You have to do re-natal use-figwheel

rastandy14:06:01

when I do re-natal use-figwheel I get an error

rastandy14:06:15

but maybe I didn’t run npm install -g react-native-cli

vikeri14:06:57

You shouldn’t have to reinstall react-native-cli

debug14:06:17

@rastandy did you reverse adb?

debug14:06:42

adb reverse tcp:8081 tcp:8081

rastandy14:06:16

I don’t need that, I’m using the virtual device

debug14:06:35

I couldn't get virtual device working myself

debug14:06:49

I also had problems

rastandy14:06:17

ok then I’ll give it a try with a real device

debug14:06:37

Yeah, make sure to do that reverse

rastandy14:06:48

yeah I know, I did that already

debug14:06:02

Yep, hope a real one works

rastandy14:06:12

I remember when I was right on my way with a project up and running, till I found that js/fetch issue 😞

debug14:06:28

Too many issues

debug14:06:03

Going back native for this project 😕

debug14:06:50

React Native is sort of unreliable when it comes to android

rastandy14:06:56

yeah, I feel frustrated, but the initial excitement when I was able to write cljs and see it run on my android device is still keeping me from giving up

debug14:06:21

Definitely, cljs is top notch

debug14:06:55

Even love how the code base started to look, but unfortunately RN is unstable

rastandy14:06:57

I’m experiencing the same, unfortunately 😞

rastandy14:06:17

I have to go, thank you guys for your help and for hearing my rants 🙂

rastandy14:06:24

have a nice day

pesterhazy17:06:50

Some day the react-native packager will finally drive me insane

pesterhazy17:06:00

is there documentation somewhere about where it looks for its node_modules dirs?

pesterhazy17:06:58

@savelichalex: I'm trying to update boot-react-native to react-native 0.27.2, and its packager has changed somehow and can't find modules in different directories anymore

pesterhazy17:06:18

and there's very little documentation on how the packager works, how it finds node modules etc.

pesterhazy17:06:43

javascript module semantics are crazy enough, but the r-n packager does its own thing again

pesterhazy17:06:21

yeah I've stared at that page many times already. --root seems to be the right option

pesterhazy17:06:30

but how it works isn't clear