I’ve been building off of @nodename’s https://github.com/nodename/AwesomeProject repo and I’m running into a problem getting om.next working with Android react-native.

is anyone else doing any work in this world (om.next + android RN) other than me and @nodename?

@adamfrey: Good question. Of the main approaches, Natal is iOS + Om Next, and Re-Natal is iOS / Android + Reagent. I don’t think I’ve seen Om Next on Android.

I did forget that re-natal supported Android. I’ll go check that out.

hey guys

is anyone seeing mounted components losing their defui class info?

https://gist.github.com/3392bbe8411e3d7f8e48

i was having issues using 'set-query' on my root component and maintaining a reference to the root-class rather than its mounted counterpart seems to have solved it

also was coming up when i was testing sends

i am using ambly, and the bug shows up when i connect using piggieback or straight from the terminal (ive seen cljs discrepancies between these two setups before :'()

i fixed the crappy formatting in my gist my b B-)

don’t know how to help, there are two reference projects that I know which works: one that I mentioned from mfikes and this one https://github.com/iamjarvo/zooborns

Maybe you can check how they work with RN

yeah ive had a fine experience up to that point of fooling around in both projects, things just started to get weird when i tested sends and set-query etc

ill try to get a nice minimal reproduction of the bugs for public consumption

could you check that it works in browsers? Maybe it’s om bug

yeah, min case would help a lot

i have a hunch that theres a discrpenancy in how instantiated components behave in rn v react

the logic branching to handle "eliding" probably needs to be extended for the rn case or something. but also it could be like a silly typo somewhere and im overconjecturing 🙃

could be yeah. Try to find a smallest case which reproduce this error and I guess someone from this channel would help