client-sdk-react-native LiveKit "Unsupported on New Architecture" Expo React Native

When a user runs npx expo-doctor on their Expo React Native app, it will show an error for LiveKit dependencies as follows:

"Unsupported on New Architecture: @livekit/react-native, @livekit/react-native-webrtc"

"No metadata available: @livekit/components-react, @livekit/react-native-expo-plugin"

The interesting thing is that LiveKit works perfectly fine in the app. It seems the metadata just needs to be updated so these warnings don't show.

Jul 01 '25 17:07 nathancovey

it's good to know... I am so nervous to migrate from expo 50 to expo 52...

Jul 06 '25 12:07 geoffcfchen

Still an issue in v54 expo too

Oct 05 '25 17:10 lancedw

+1 would love to see new architecture support

Oct 23 '25 18:10 coryetzkorn

Same here

Dec 01 '25 13:12 AhmadMancy

As per https://github.com/livekit/client-sdk-react-native/issues/134#issuecomment-3428104357 it does seem to me that the new architecture is supported through the use of the interop layer? The reason expo-doctor reports it's not is the package's entry in the React Native directory - fixing this might be as simple as submitting a PR like the one I did for Realm here: https://github.com/react-native-community/directory/pull/1210

Jan 12 '26 14:01 kraenhansen

Opened https://github.com/react-native-community/directory/pull/2114 to fix the entries in the https://reactnative.directory 🤞

Jan 13 '26 15:01 kraenhansen

React native directory entries are updated.

Jan 19 '26 23:01 davidliu