@plins check that you can load those files in your browser

if you cannot - then no way your app will be able to

I can

if you can, then just run a Metro refresh - sometimes there's a hiccup

type r in the Metro terminal

you should not have to mess w/ anything else

ClojureScript files are fetched through Metro

if Metro is not working - then nothing is going to work anyway

(the RN bundle has to be served through Metro)

if I press R I get the same results 😕 what is strange to me is that if I run the hello world app created with npx react-native init it works fine, Metro is working and I can hotreload code Im going to double check my configuration and try it on another machine to see if things work out differently, thanks for the assistance everyone 🙂

like I said I would not look too deeply for answer

you already know there's something quite contradictory here

you can load those urls in a browser - but the Metro network request for those files is failing

Anyone know what translating this into cljs looks like?

<CountdownCircleTimer>
    {({ remainingTime, animatedColor }) => (
      <Animated.Text style={{ color: animatedColor }}>
        {remainingTime}
      </Animated.Text>
    )}
  </CountdownCircleTimer>

(def text (r/adapt-react-class (.-Text ReactNative)))
(def countdown (r/adapt-react-class CountdownCircleTimer))
[countdown
      (fn [^js props]
        (let [remaining-time (j/get props :remainingTime)
              color (j/get props :animatedColor)]
          (r/reactify-component
           [text
            {:style {:color color}}
            remaining-time])))]

@alex395 I guess that's a weird JSX shorthand instead of inlining the props as attributes?

I don't think it's specific to RN

You could probably look at what the JSX translates to, I'm not familiar with that pattern myself

Yeah I’ve not seen it before either… I am wondering if its something to do with reagent generating class components and those somehow aren’t compatible with what the CountdownCircleTimer wants, but I feel really out of my depth there 😅 I guess I will ask in #reagent as that seems more appropriate

Well looks like I just had to use r/as-element instead of reactify-component, doesn't make much sense to me.. guess I'm seeing the advantages of helix now, gets out of the way and is easier to reason with