[0.0.18] invalid value passed to interaction

[hirbod]

Hi @nandorojo,

tried the Canary and so far, everything was working as expected without breaking changes.
While I tried your release-note example, which was looking dope, I encountered this issue:

<MotiPressable>
  {(interaction) => {
    return (
      <MotiView
        animate={() => {
          'worklet'

          const { pressed, hovered } = interaction.value

          return { opacity: pressed ? 0.9 : 1 }
        }}
      />
    )
  }}
</MotiPressable>

Some informations:

• react-native-reanimated v2.5.0
• react-native-gesture-handler v2.1.1
• moti v0.18.0-alpha.10

[nandorojo]

Hmm weird, thanks for sending. I haven't tried reanimated 2.5 yet, I wonder if that's related (I'm on 2.3).

[hirbod]

FYI: if you're using a custom-dev-client like I do, you will need to disable expo autolinking for rea inside the package.json since its not working with 2.5.0 currently.

  "expo": {
    "autolinking": {
      "exclude": [
        "react-native-reanimated"
      ]
    }
  },

[nandorojo]

I reproduced this in my app, will investigate.

[nandorojo]

Dealing with reanimated internals is tricky! Think I got it, will push shortly.

[hirbod]

I am dealing with those internals since 3 days to fix an ugly bug but I am close to give up!
Thanks for investigating

[nandorojo]

Hm, reanimated may not allow this specific case for some reason. Going to try to repro and send a PR. Thought I had it working, might have been mistaken.

[nandorojo]

It will work for the animate prop, but the child as a function may not work out of the box yet.

[nandorojo]

Here is a reproduction that shows it's not possible with Reanimated: https://snack.expo.dev/@beatgig/courageous-bubblegum

Will open an issue there.

[nandorojo]

Opened an issue: software-mansion/react-native-reanimated#3123

[nandorojo]

Closing for now since it's a reanimated issue. Will make a note of this on the canary release notes.

[hirbod]

Closing this will most likely cause duplicate reports, or?