This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-21
Channels
- # admin-announcements (2)
- # aws-lambda (2)
- # beginners (26)
- # boot (179)
- # cider (36)
- # cljs-dev (118)
- # cljsrn (23)
- # clojure (150)
- # clojure-android (1)
- # clojure-austin (7)
- # clojure-austria (3)
- # clojure-canada (1)
- # clojure-dev (7)
- # clojure-dusseldorf (4)
- # clojure-germany (3)
- # clojure-greece (34)
- # clojure-nl (4)
- # clojure-quebec (9)
- # clojure-russia (30)
- # clojure-spec (38)
- # clojure-uk (3)
- # clojurescript (46)
- # clr (1)
- # core-async (2)
- # css (2)
- # cursive (17)
- # datomic (12)
- # devcards (8)
- # dirac (1)
- # docker (2)
- # hoplon (216)
- # jobs (2)
- # kekkonen (1)
- # lein-figwheel (18)
- # leiningen (2)
- # luminus (1)
- # mount (4)
- # off-topic (2)
- # om (15)
- # onyx (1)
- # parinfer (1)
- # pedestal (2)
- # planck (26)
- # reagent (98)
- # spacemacs (6)
- # specter (19)
- # spirituality-ethics (54)
- # untangled (22)
- # vim (24)
- # yada (4)
@alwx: I tried bumping figwheel to a newer version to fix the console println woes but it seems the luno example doesn't work anymore
e.g. this simple change doesn't work anymore https://github.com/Macroz/luno-react-native
guys, can anyone enlighten me about rn's bundling when targeting release? i'm not sure why my images are not included (and thus the application fails when run on my physical android phone) all is well when i am running via figwheel (i'm require'ing the static images), but with prod-build this doesnt seem to work?
@balint: react packager work with images in prod
when i checked my phone's logs via adb logcat after the app crashed i saw it was complaining about requiring unknown module (and the module was the image path i gave it in my cljs)
@alwx I resolved my figwheel issues by removing the clean-targets from luno example, I've sent a couple pull requests if you are interested
@macroz thanks very much for your investigation and fixes. will check your pull requests later today
@balint: And you’re requiring the images with (js/require “imagepath/imagefile.png”)
?
@seantempesta: to be exact: (js/require "./images/imagefile.jpg")
hmm, not sure then. I haven’t had any problems, but I haven’t tried building for Android
are the require statements making it into the production build file?
i found this, will have to investigate if gradle runs this: https://github.com/facebook/react-native/issues/8230
well, the react packager should be scanning for those statements and bundling any images
has anybody an idea why my adb does not have a "reverse" command? I have adb 1.0.31 installed. In react-native and in re-natal docu they say I should run "adb reverse" but this command does not exists and is also not mentioned in the adb documentation ( https://developer.android.com/studio/command-line/adb.html#commandsummary )
damn, I used the version 1.0.31 that was installed by apt-get and not the current version 1.0.36 which was installed by the android sdk. the android studio documentation tricked me because it is completely out of date....
@seantempesta: figured out: somehow react-native bundle
generates the assets' names like this: from require("./images/nice.jpg");
it becomes: "projectName/images/nice.jpg"
where projectName comes from the package.json name... but why?!
(if i adjust my requires in cljs to include the project name, i can start up the app on my android phone)
@knotschi: also as I know this work in android 5+
@balint: haha. I ask myself why all the time too. Good to hear you figured it out. 🙂