For anybody using krell on Ubuntu with Android Studio and the Android Studio emulator, in addition to the steps described on github and the react native page, I had to run npm start in the project directory to get it to serve the files to the emulator.

@mac that's a bit odd - was pretty sure npx react-native run-foo would do that for you?

Anyone here who have used the react-native-gesture-handler? I am trying to get this example working.

This is what I have done:

The (.-state nativeEvent) thing is just nil (it seems so). When using the .equals function that if does return true, and the alert does popup, but it does so on any kind of press not just longpress 😮

Yeah the problem is that (.-state nativeEvent) is nil no matter what. Am I accessing it wrong? nvm! When in doubt, use (js-keys javascriptObject) 😄 I got a list of all the attributes, and obviously I wasn't accessing the correct one from start. Need to do (.-state (.-nativeEvent events)).

@dnolen Apparently not.

@mac so a known react native issue?

@dnolen If I read this https://reactnative.dev/docs/environment-setup#native correctly it is not an issue but necessary to run the app. You need both npx react-native start (or npm start) and npx react-native run-android. So you might want to add it to the krell reagent tutorial.

huh ok, locally I've always seen the bundler auto start with run-android

@shakof91 just to get a long press handling, why don’t you try this:

...
(:require [reagent.core :as r])

(def react-native (js/require "react-native"))
(def touchable-opacity (r/adapt-react-class (.-TouchableOpacity react-native)))
[touchable-opacity {:on-long-press #(js/alert "long press")}
   [text {} "long press"]]

@dnolen @mac Yeah, same behavior for me on one of my setup (Ubuntu/Android Studio). I must always open one terminal to run npx react-native start and another for npx react-native run-android. Dunno why it's not always the case...depend on "something" in the setup

Ok will update the docs

updated the docs