hi @vikeri, how you adapt font size and other properties based on screen size?

I’m pretty much interested

@vikeri: also, how do you updated re-natal to [email protected]

I’m the only one encountering problems? 🙂

@rastandy: We recently talked about it. You need upgrade re-natal (this is only update re-natal) and then update react-native, see https://facebook.github.io/react-native/docs/upgrading.html

I remember that read about «em» in RN

hope found it

@rastandy: well RN exposes a Dimensions object. With that you can get the screen width and height. And with that you have a dynamic font size based on the screen size. Eg. Over 400px wide gives a base font size of 16 and below you have 14 or something.

@vikeri: You need also PixerRatio

@vikeri: I didn’t know, great!

@vikeri, thank you very much, I’ll check it out

I think that if calculate font-size based on Dimension and PixelRatio we get smth like «em» in web)

ok, thank @savelichalex

I need to check this out, I’m a newbie on RN

any suggestion on how to upgrade my re-natal om-next project to RN 0.27?

I’m getting some strange EOF errors when fetching data from the web

maybe some RN bug

@rastandy: show error

@savelichalex: ok, just a sec

Got JS Exception: SyntaxError: Unexpected EOF 06-15 03:50:11.547 1628 1714 E unknown:React: Exception in native call from JS 06-15 03:50:11.547 1628 1714 E unknown:React: java.lang.RuntimeException: SyntaxError: Unexpected EOF (<unknown file>:1) 06-15 03:50:11.547 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method) 06-15 03:50:11.547 1628 1714 E unknown:React: at android.os.Handler.handleCallback(Handler.java:739) 06-15 03:50:11.547 1628 1714 E unknown:React: at android.os.Handler.dispatchMessage(Handler.java:95) 06-15 03:50:11.547 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31) 06-15 03:50:11.547 1628 1714 E unknown:React: at android.os.Looper.loop(Looper.java:148) 06-15 03:50:11.547 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:187) 06-15 03:50:11.547 1628 1714 E unknown:React: at java.lang.Thread.run(Thread.java:818) 06-15 03:50:11.550 1628 1714 I ReactNativeJS: ERROR FETCHING FEED: [:feeds/feed-by-url http://www.cmcc.it/events?feed=events] 06-15 03:50:11.556 1628 1714 E ReactNativeJNI: Got JS Exception: SyntaxError: Unexpected EOF 06-15 03:50:11.557 1628 1714 E unknown:React: Exception in native call from JS 06-15 03:50:11.557 1628 1714 E unknown:React: java.lang.RuntimeException: SyntaxError: Unexpected EOF (<unknown file>:1) 06-15 03:50:11.557 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method) 06-15 03:50:11.557 1628 1714 E unknown:React: at android.os.Handler.handleCallback(Handler.java:739) 06-15 03:50:11.557 1628 1714 E unknown:React: at android.os.Handler.dispatchMessage(Handler.java:95) 06-15 03:50:11.557 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31) 06-15 03:50:11.557 1628 1714 E unknown:React: at android.os.Looper.loop(Looper.java:148) 06-15 03:50:11.557 1628 1714 E unknown:React: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:187) 06-15 03:50:11.557 1628 1714 E unknown:React: at java.lang.Thread.run(Thread.java:818)

ups sorry

to much text here

@rastandy: oh my) ok, smth wrong with js. Are you sure that all fine with your code? Are you try to remove node_modules and install them again?

@rastandy: maybe this is issue will help you https://github.com/facebook/react-native/issues/4407

@savelichalex: I’m pretty sure my code works because it happens with some feeds (i’m downloading xml feed data) and not others

I’ve seen that issue on github

I think that’s my problem

@rastandy: I had some problems with fetch on android, but after upgrade to 0.27 this problems were solved for me

@savelichalex: oh yeah? fetch problems are fixed?

@pesterhazy: Looks like yes) On 0.25 I have an error with isomorphic-fetch, but after upgrade to 0.27 all works fine

@savelichalex: thanks! That’s what I hoped and why I would like to upgrade

but had problems with the re-natal upgrade

I need to sort it out

@savelichalex: cool. what's isomorphic-fetch?

@rastandy: ok, step by step what i’m do: 1. re-natal upgrade 2. npm i [email protected] —save 3. react-native upgrade (this is can overwrite some your files, make backup before do it, if you change some, for ie build.gradle) 4. check dependensies in package.json (i have [email protected] and [email protected]) 5. maybe you need to drop node_modules and do npm i if you have any trouble that’s all

@pesterhazy: looks like that everybody using this for fetch) there is simple library that return node-fetch for node, whatwg-fetch for web and so on, but looks like this library doesn’t maintained anymore and have bugs. I thought that in 0.27 they drop isomorphic-fetch as dependency

@savelichalex: thanks for the explanation

@pesterhazy: big problem for js community is low quality packages) that’s why i love clojure)

@savelichalex: thanks for describing your steps

@savelichalex: I did pretty the same but with react-native 0.27.0. Need to try 0.27.2

I had some errors in the figwheel bridge javascript file

I’ll give it a try again and report errors if I’ll encounter them

@savelichalex: many thanks again for your help

may I paste errors I’ve found after upgrading my om-next app?

it’s not too much text

@rastandy: just paste it on snippet)

is snippet a slack channel?

↙️ create snippet

ok, need to find it 😄

found it 😄

@rastandy: What the 49 line?

don’t know in which file I should look at

directly into the packager bundle?

totally worthless stack traces 😄

Not sure that in bundle

But check it)

I’m lost. Now I’m trying to build it thorugh lein prod-build

because maybe the problem is in figwheel-bridge.js

Nice idea, I’m always trying lein prod-build because there is a way to get all compile time errors 😉

no luck

it’s a problem in defui from om-next

clim_earth.android.core.Feed.prototype = goog.object.clone(React.Component.prototype);

not that om-next has a bug

but React.Component.prototype is null

oh yeah, solved this problem, but found that a library i’m using is incompatible with okhttp3 library

also found the same problem in js/fetch

wow

lucky day 😄

i.e. my EOF error when fetching xml data from the network is not solved