Upgrading to rc6 generate reanimated issues

[wcastand]

What happened?

it looks like uniwind latest update tries to load reanimated before it's initialized properly.

Cannot read property 'CurvedTransition' of undefined

maybe some info from claude code can be useful, sorry he created an issue automatically not well formatted.

#462

Steps to Reproduce

1. update to rc6
2. build ios
3. launch and get the error trying to load the app

Snack or Repository Link (Optional)

No response

Uniwind version

npm:uniwind-pro@1.0.0-rc.6

React Native Version

0.83.2

Platforms

iOS

Expo

Yes

Additional information

• I've searched for similar issues in this repository and found none
• I am a Uniwind Pro user

[Brentlok]

Hi, I've launched separated expo project with rc.6, works first try without any issues. We also have a more complex expo app for testing uniwind-pro (multiple screens with all components, animations, inline styles being used) and it also works fine

Can we get some more details? Or could you create a separated repo with minimal reproduction?

[wcastand]

wondering if it's more link to updating to latest xcode ios26.3
we also have issues with emoji rendering since then :/

[wcastand]

so tried to look into why it breaks on our repo only when upgrading to rc6.
claude code managed to get it working so will share what i found with CC.

The npm pre/ directory (postinstall scripts, CLI) is identical between rc.5 and rc.6 — the only diff is the version string in
package.json. But the actual runtime code (dist/, src/) is downloaded via postinstall from their CDN based on the version number.

  So the resolver bug likely existed in rc.5 too, but something in rc.6's downloaded runtime changed the import graph — probably core/native/store.ts
now eagerly imports from react-native-reanimated and ../reanimated where rc.5 may have done it lazily, or the View component didn't previously go
through core/native/store.ts. I can't verify because the downloaded code requires authentication to fetch.

  You could mention: "The resolver's isFromReactNative check has likely always been too narrow, but rc.6 appears to have changed the internal import
graph so that store.ts now eagerly pulls in reanimated, making the circular dependency reachable for the first time."

Uniwind rc.6's metro nativeResolver creates a circular dependency with react-native-reanimated, crashing the app at startup.

  The cycle:

  1. Any early module → require('react-native-reanimated')
  2. Reanimated initializes → its src/component/View.ts does require('react-native')
  3. Metro resolver redirects react-native → uniwind/components (because the isFromReactNative check looks for /react-native/ in the path, which
  doesn't match /react-native-reanimated/)
  4. uniwind/components View getter → core/native/store.ts → require('react-native-reanimated') — circular! Reanimated hasn't finished initializing
  5. Metro returns partially initialized module → _layoutReanimation is undefined → TypeError: Cannot read property 'CurvedTransition' of undefined

  The bug in the resolver (dist/metro/index.cjs line 86):

  const isFromReactNative = context.originModulePath.includes(`${sep}react-native${sep}`)

  This matches /react-native/ but not /react-native-reanimated/, so imports from reanimated are not excluded from the redirect.

  Fix needed: The resolver should also skip redirection when originModulePath is inside react-native-reanimated (and likely any other RN library that
   imports from react-native internally).

  Workaround (in user's metro.config.js):

  const finalConfig = withUniwindConfig(wrapWithReanimatedMetroConfig(config), { ... })

  const uniwindResolveRequest = finalConfig.resolver.resolveRequest
  finalConfig.resolver.resolveRequest = (context, moduleName, platform) => {
    if (
      moduleName === "react-native" &&
      context.originModulePath.includes(`${require("path").sep}react-native-reanimated${require("path").sep}`)
    ) {
      return context.resolveRequest(context, moduleName, platform)
    }
    return uniwindResolveRequest(context, moduleName, platform)
  }

  module.exports = finalConfig

not sure how specific to our repo it is tho, i let you see if what i found to fix the issue on our repo makes sense globally

the metro fix

// Prevent circular dependency: when react-native-reanimated imports "react-native",
// uniwind's resolver redirects it to uniwind/components, which loads store.ts,
// which requires react-native-reanimated back — before it finishes initializing.
// Fix: bypass uniwind's redirect for imports originating from react-native-reanimated.
const uniwindResolveRequest = finalConfig.resolver.resolveRequest
finalConfig.resolver.resolveRequest = (context, moduleName, platform) => {
	if (
		moduleName === "react-native" &&
		context.originModulePath.includes(`${require("path").sep}react-native-reanimated${require("path").sep}`)
	) {
		return context.resolveRequest(context, moduleName, platform)
	}
	return uniwindResolveRequest(context, moduleName, platform)
}

[Brentlok]

Just to give some context on the code snippet -we're using dynamic imports there to avoid circular dependencies.

It's a bit tricky for us to figure out exactly what's going wrong without seeing your code. We test uniwind-pro across several apps before every release to make sure things don't break.

You've mentioned that rc.5 is working, but it was already using reanimated components. Because of that, we suspect it might be clashing with another dependency you have installed or your specific use case / config. Could you put together a small reproduction for us? If your code is private, feel free to share the repo with us in a private message. Once we can see the issue in action, we'll get it fixed ASAP!

[wcastand]

https://github.com/wcastand/uniwind-repro

when i try to build ios, i get the error
it seemst to be related to the fact that we import reanimated early.

global import generate the issue, i also tried in my local repo to remove it but it still happens because we use useReducedMotion early in the init of the app for config observable so just removing the global import doesn't fix the issue.

[SrAnthony]

Btw I'm having the same problem on android and ios, the metro fix works for me.
On my case the ios app would just hang on the the splash screen with "Downloading 100%..." from expo. The error only appeared on android.

[Brentlok]

I was able to fix it, it will be available in the next release

[jpudysz]

Released in RC.7