[expo-modules] Move code from `unimodules` into `expo-modules-core` (#13703)# Why Migrated `unimodules-core`, `unimodules-react-native-adapter`, `unimodules-app-loader` into `expo-modules-core`
[expo-modules] Move code from `unimodules` into `expo-modules-core` (#13703)# Why Migrated `unimodules-core`, `unimodules-react-native-adapter`, `unimodules-app-loader` into `expo-modules-core` # How - Change package using AS refactor tools - Fix some places where AS wasn't able to do automatically - Fix compatibility with new auto-linking - Ensure that classes which are used during installation steps are still available in the old place # Test Plan - expo-go (tested using unversioned and 41) - bare-expo
show more ...
[expo-branch] Upgrade react-native-branch to 5.0.0 (#10204)# Why We want to remove IDFA code from iOS apps. # How Used `expotools`. On Android created a new `BranchIntentNotifier` which us
[expo-branch] Upgrade react-native-branch to 5.0.0 (#10204)# Why We want to remove IDFA code from iOS apps. # How Used `expotools`. On Android created a new `BranchIntentNotifier` which uses unimodules infrastructure to notify `RNBranchModule` of new Intents. # Test Plan Both Expo clients compiled.
[react-native-branch] Upgrade to 5.0.0-rc.1 (#9625)# Why Cutoff approaches. # How - Used expotools - Manually upgraded native dependencies - [android] Removed `InstallReferer` reference
[react-native-branch] Upgrade to 5.0.0-rc.1 (#9625)# Why Cutoff approaches. # How - Used expotools - Manually upgraded native dependencies - [android] Removed `InstallReferer` reference - [ios] Added compiler variable to `EXBranch` pod # Test Plan All (iOS, Android) x (Expo client, Bare Expo) compiled.
Upgrade vendored modules (#6176)# Why As per the output of `gulp outdated-vendored-modules`: Outdated native modules: - DISMISS @expo/vector-icons: 10.0.0 bundled, latest on NPM is 10.0.6 -
Upgrade vendored modules (#6176)# Why As per the output of `gulp outdated-vendored-modules`: Outdated native modules: - DISMISS @expo/vector-icons: 10.0.0 bundled, latest on NPM is 10.0.6 - DONE @react-native-community/netinfo: 3.2.1 bundled, latest on NPM is 5.0.0-rc.1 - SWIFT-BLOCKED lottie-react-native: 2.6.1 bundled, latest on NPM is 3.2.1 - DONE react-native-branch: 3.1.1 bundled, latest on NPM is 4.2.1 - #6127 react-native-gesture-handler: 1.4.1 bundled, latest on NPM is 1.5.0 - DONE react-native-maps: 0.25.0 bundled, latest on NPM is 0.26.1 - DONE react-native-reanimated: 1.3.0 bundled, latest on NPM is 1.4.0 - WAIT-FOR-STABLE react-native-screens: 1.0.0-alpha.23 bundled, latest on NPM is 2.0.0-alpha.7 - DONE react-native-svg: 9.9.5 bundled, latest on NPM is 9.13.3 - DONE react-native-view-shot: 2.6.0 bundled, latest on NPM is 3.0.2 - DONE react-native-webview: 7.0.5 bundled, latest on NPM is 7.4.3 - #6162 react-native-appearance: 0.1.0 bundled, latest on NPM is 0.2.0-rc.0 - DONE react-native-safe-area-context: 0.5.0 bundled, latest on NPM is 0.6.0 BTW fixes https://github.com/expo/expo/issues/6165. # How Upgraded each module with an `expotools` command, checking after each one that the NCL tests pass. # Test Plan Manual NCL tests were ok.
Migrate to androidx (#5521)# Why resolves: https://github.com/expo/expo/issues/5260 # How https://developer.android.com/jetpack/androidx/migrate https://blog.danlew.net/2018/11/14/the-rea
Migrate to androidx (#5521)# Why resolves: https://github.com/expo/expo/issues/5260 # How https://developer.android.com/jetpack/androidx/migrate https://blog.danlew.net/2018/11/14/the-reality-of-migrating-to-androidx/ https://gist.github.com/loganj/7535a13e98be83460f362b63dbd13e07 # Test Plan Run NCL, native tests (androidTest, test)
[expo-branch] Change package of vendored expo-branch (#5668)
[expo-branch] First 3rd party library unimodule wrapper! (#5165)# Why We would like to provide a way to users to optionally include `react-native-branch` in their standalone apps. Fixes https://
[expo-branch] First 3rd party library unimodule wrapper! (#5165)# Why We would like to provide a way to users to optionally include `react-native-branch` in their standalone apps. Fixes https://github.com/expo/expo/issues/5132. # How I added support for React Native-specific unimodules to React Native adapter. Right now it works like this: - unimodule `expo-branch` depends on `react-native`, so it can use its API. It's no longer a uni-platform module, more an optinmodule (I guess the name won't stick) - we copy `react-native-branch` vendored module directly to the unimodule. It will compile, since we added necessary dependencies to the unimodule - `BranchPackage < org.unimodules.Package` implements `ReactPackage` interface too, forwarding all the calls to the vendored `RNBranchPackage`. - when the module registry provider creates a module registry from a list of `Packages`, it can filter out `ReactPackages` — and so it does, putting them into a local internal module (`ReactPackagesProvider`) which only purpose is to carry those to `ModuleRegistryAdapter` which is responsible for creating a list of React Native modules out of a module registry. The adapter grabs the `ReactPackagesProvider` and adds React Native modules to the list. # Test Plan I have confirmed that adding `BranchPackage` to a list of installed unimodules' packages creates `RNBranchModule` and exports to JS.