This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-28
Channels
- # ai (1)
- # beginners (190)
- # boot (24)
- # cider (43)
- # cljsjs (3)
- # cljsrn (29)
- # clojars (6)
- # clojure (310)
- # clojure-dev (6)
- # clojure-nl (6)
- # clojure-russia (11)
- # clojure-spec (66)
- # clojure-uk (95)
- # clojurescript (103)
- # clojurewerkz (2)
- # core-async (9)
- # cursive (4)
- # datomic (5)
- # hoplon (163)
- # lein-figwheel (52)
- # off-topic (6)
- # om (6)
- # onyx (42)
- # perun (8)
- # re-frame (16)
- # reagent (10)
- # ring (7)
- # ring-swagger (1)
- # rum (1)
- # slack-help (2)
- # uncomplicate (1)
- # untangled (80)
Hi, I've successfully connected to a boot cljs repl on Android, but each time reloading show me this error: console.error: "Websocket REPL error:occupied". Boot newbie.
how do you guys usually persist data? I was thinking of using realm-react-native and add some events that automatically write db-atom content into realm / loading it on app start
wondering how fast it would be to directly read out of realm and skip the atom for actual data. Use the db atom as temporary state only
@tiensonqin I remember some websockets issues android a while back
@tiensonqin have you forwarded the port using adb reverse
?
Yeah, I've tried as below: adb reverse tcp:8081 tcp:8081 adb reverse tcp:8079 tcp:8079 adb reverse tcp:9001 tcp:9001
@vikeri Yeah, same error. Haven't checked the issues, 🙂
@tiensonqin I think there might be a problem with Android in React Native, since it works well on iOS. But it could also be a problem with boot-reload. Interestingly enough there seems to be a port of figwheel to boot-reload, so maybe this issue will be solved.
I dug around in Android websocket land but I’m not the websocket master so no luck so far...
@dvcrn We serialize using transit (even though it’s not recommended) #badboy and then put it in asyncStorage. Would be really nice if you could use Realm directly though!
@tiensonqin would love to resolve this
if you can find the root cause I can help debug
@pesterhazy @vikeri Thanks, I'll investigate to this problem later.
I'm working to add boot support to Exponent, I'm already fall in love with boot.
@pesterhazy @tiensonqin I think the issue is a websocket not being closed when you reload the javascript without reloading the native app. But I’m definitely not sure...
@tiensonqin Sweet!
could be an issue in boot-reload then
it shouldn't try to re-open the websocket when reloading, for sure
@tiensonqin exponent support would be amazing!
Currently reloading sometimes works, sometimes not works. So maybe it's my fault.
@tiensonqin Have the exact same issue, so I doubt it’s your setup. I think I reproduced it in the example repo as well.
@pesterhazy Nice to hear, @jorda0mega already created a working example: https://github.com/jorda0mega/boot-react-native-exponent-template
@vikeri I'll check your example too. Have to go now, will report later.