Release 3.1.0-rc.1

[Azhi-10133]

hi dears

We're planning to upgrade production apps to Expo SDK 58 (RN 0.88). On 3.0.7, the app crashes on launch, because NativeComponentRegistry is missing from the react-native wrapper's export list.

3.1.0-rc.0 fixes that one, but AssetRegistry (used by expo-asset) still looks missing.

Two questions:

Is the RC considered safe for large-scale production apps?
Is there a timeline for a stable release?

[omerfarukgurbuz]

I checked this specific import path in the published packages. expo-asset@58.0.20 imports AssetRegistry from the root react-native module, and the RN 0.88.0 root exports both AssetRegistry and NativeComponentRegistry. The CSS package redirects the root import to its components wrapper, whose CommonJS build forwards enumerable RN exports. So the lack of those two literal names in the wrapper file doesn't by itself show that either export is missing.

I also ran expo export --platform android with Expo 58.0.23, RN 0.88.0, expo-asset@58.0.20 and react-native-css@3.1.0-rc.1. The fixture imported both registries, imported Asset, and included a static PNG. Metro produced the Hermes bundle and the PNG asset. That checks bundling only. I didn’t install or launch a release APK.

If you still see the crash on RC1, I’d reproduce it on the same build with withReactNativeCSS(getDefaultConfig(__dirname)) as the only Metro wrapper, then add the other wrappers back one at a time. Include the first native stack frame and the resolved versions from npm ls react-native react-native-css expo-asset in the repro. The RC1 notes still give Expo 57 as the tested baseline. I didn’t find an announced stable date or an Expo 58 production compatibility claim there. Package inspection and the export check were done with Codex.