Expo requirements and limitations

Requirements

• @aetherpush/react-native-code-push 1.2.1 or newer; the plugin declares it as a peer dependency.
• Expo SDK 53 or newer. The plugin needs the Swift AppDelegate template Expo introduced in SDK 53. On older projects, integrate the SDK manually following its own setup guides.
• A development build or a prebuild workflow. The plugin changes native files, so it does not work in Expo Go.

expo-updates must be inactive

Aether and expo-updates both control the JavaScript bundle and cannot run together. The plugin checks at prebuild and fails with a clear error when an active expo-updates install is found:

expo-updates is installed and enabled. Aether and expo-updates both control the JS bundle
and cannot run together. Uninstall expo-updates, or set updates.enabled to false in your
app config.

Custom native templates

The plugin edits the files expo prebuild generates from the Expo template. A project with a custom AppDelegate or MainApplication that no longer matches the template stops the plugin with an error that tells you what to wire manually.

The version gap below Expo SDK 53

The SDK itself supports React Native 0.76 and newer, but Expo SDK 53 ships React Native 0.79. An Expo app on SDK 52 (React Native 0.76) meets the SDK’s React Native floor and still cannot use this plugin. The route there is manual integration with the SDK’s platform setup guides, as with any pre-53 project.