RNSharedElementTransition is not available

[prrrcl]

Im using react-native-cli project. Im using react-navigation 5 and your prerelease tag.

when i use Expo, i havent got any problem, but on Shared screen this message appear: RNSharedElementTransition is not available, did you forget to link react-native-shared-element into your project?

is a bug? i linked manually but i havent got nothing

[nicoache1]

Same issue happens to me with a vanilla React-Native app. Check in Xcode and it seems that the library is installed in the pods.

[IjzerenHein]

Hi, please provide a full repo containing the exact steps that you performed.
Most likely, the project is not linked correctly into your XCode workspace.

[prrrcl]

Same issue happens to me with a vanilla React-Native app. Check in Xcode and it seems that the library is installed in the pods.

Yeah, it is installed :/

[KochMario]

Not sure if it helps, but I initially had the same problem and warning message on androd.
For me personally it was due to another error in my build process, that's why android was never built successfully after I added react-native-shared-element.
Once I fixed the other (unrelated) build error, the build process succeeded and react-native-shared-element was linked / included correctly.
(I'm using react-navigation 5 and the rreact-navigation-shared-element prerelease as well.)

Does your error appear on android or ios?

[BATTLEROYALXS]

Same problem here ! :(

[Alarees]

i'm having the same issue here.

• "react-native-shared-element": "^0.7.0"
• "react-navigation-shared-element": "^5.0.0-alpha1" // pre-release
• react-navigation 5

[Alarees]

i solve the problem :

1. react-native link react-native-shared-element

optionally link when needed as in README

2. re-build the code npx react-native run-android

[longtq-younet]

I solve the problem:
go to Podfile -> Add pod 'RNSharedElement', :path => '../ios/node_modules/react-native-shared-element'

[IjzerenHein]

It looks like the code is not linked correctly. On React Native 0.59 or lower the native code needs to be linked manually. Either by using react-native link react-native-shared-element or by manually updating the ios/Podfile (and running npx pod install) and the Android project.

As of React Native 0.60, linking is performed automatically.

[amirbhz86]

I think it is because install wrong module
remove all modules include react navigation and react native share elements
then install them again

dont forget to "pod install" in ios directory

[MarcHbb]

I have the same issue with expo, using react navigation v6

[robhern135]

This is still an issue in expo with react navigation 6

[joelsoncastro]

I am also having this issue in expo this is my dependency list:

"dependencies": {
    "@react-navigation/bottom-tabs": "^6.5.11",
    "@react-navigation/material-top-tabs": "^6.6.5",
    "@react-navigation/native": "^6.1.9",
    "@react-navigation/stack": "^6.3.20",
    "@types/react": "~18.2.14",
    "expo": "~49.0.15",
    "expo-status-bar": "~1.6.0",
    "ms": "^2.1.3",
    "react": "18.2.0",
    "react-native": "0.72.6",
    "react-native-gesture-handler": "~2.12.0",
    "react-native-pager-view": "^6.2.2",
    "react-native-reanimated": "~3.3.0",
    "react-native-safe-area-context": "^4.7.3",
    "react-native-screens": "~3.22.0",
    "react-native-scrollable-tab-view": "^1.0.0",
    "react-native-svg": "^13.14.0",
    "react-navigation-shared-element": "^3.1.3",
    "typescript": "^5.1.3"
  },

[melnikovkolya]

@joelsoncastro

Since you are using expo version >49, the react-native-shared-element is still available, but you need to run expo run:ios/android, since it only works in the development builds.

E.g., there is this note at the header of the page https://docs.expo.dev/versions/v48.0.0/sdk/shared-element/

In SDK 49 and higher, this library will no longer be available in [Expo Go](https://docs.expo.dev/get-started/expo-go). You can still use it with [development builds](https://docs.expo.dev/develop/development-builds/introduction).

[joelsoncastro]

Hi @melnikovkolya,

You are right. I was using the Preview Build, assuming it was the same thing. I had a go at it today and it worked straight ahead.

Thank you very much

[jakeherm]

I am having this same issue. How were people able to solve it?