This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-11
Channels
- # arachne (5)
- # beginners (28)
- # boot (59)
- # cider (10)
- # cljs-dev (10)
- # cljsrn (10)
- # clojure (58)
- # clojure-brasil (2)
- # clojure-czech (9)
- # clojure-miami (1)
- # clojure-poland (2)
- # clojure-russia (12)
- # clojure-spec (16)
- # clojure-sweden (1)
- # clojure-taiwan (1)
- # clojure-uk (77)
- # clojurebridge (3)
- # clojurescript (108)
- # cursive (5)
- # datomic (25)
- # defnpodcast (2)
- # editors (1)
- # events (1)
- # funcool (24)
- # hoplon (37)
- # instaparse (1)
- # lein-figwheel (7)
- # leiningen (7)
- # luminus (3)
- # off-topic (9)
- # om (90)
- # onyx (88)
- # proton (3)
- # protorepl (9)
- # re-frame (30)
- # reagent (23)
- # rethinkdb (2)
- # untangled (33)
- # vim (1)
- # yada (6)
Anyone else running 0.29.0
? I tried the new react-native log-ios
command and even though the app is working as expected I constantly get this error reported in the console:
assertiond[43292] <Error>: assertion failed: 15F34 13E230: assertiond + 15801 [3C808658-78EC-3950-A264-79A64E0E463B]: 0x1
@vikeri: I was able to get everything back and hooked up on 0.29.0. I don’t see that error.
@vikeri: assertiond errors are a dime a dozen
we have literally dozens of them. I just ignore them
although of course I'd love to know where they come from
(I'm still on 0.19 so this is not a new phenomenon)
@boorad: just to clarify, you don't get any output in the native console (native not being the chrome console)?
@pesterhazy: haha alright. Yes it is mystery indeed.