Remove some unimodules leftovers from the repo
Remove deprecated unimodules packages from repository (#14585)
Publish expo, expo-modules-core[email protected]
Publish packages@unimodules/[email protected]@unimodules/[email protected][email protected][email protected][email protected][email protected]expo-analytics-s
Publish packages@unimodules/[email protected]@unimodules/[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]@expo/[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
show more ...
[expo-modules][ios] Fix errors from use_frameworks in Podfile (#14523)# Why close [ENG-1772](https://linear.app/expo/issue/ENG-1772/regression-test-for-use-frameworks-in-podfile) fixes #13920
[expo-modules][ios] Fix errors from use_frameworks in Podfile (#14523)# Why close [ENG-1772](https://linear.app/expo/issue/ENG-1772/regression-test-for-use-frameworks-in-podfile) fixes #13920 # How - error: `The 'App' target has transitive dependencies that include static binaries` declare `static_framework = true` in podspec. since all expo-modules ship in either source code or static xcframework, it should make sense to add `static_framework` declaration and solve this kind of errors. - error: generated swift runtime header not found fix like this because in framework mode, generated headers are inside module. ```diff +#if __has_include(<ExpoModulesCore/ExpoModulesCore-Swift.h>) +// For cocoapods framework, the generated swift header will be inside ExpoModulesCore module +#import <ExpoModulesCore/ExpoModulesCore-Swift.h> +#else #import "ExpoModulesCore-Swift.h" +#endif ``` - error: [gl] `<cassert>` import not found this is supported in c++, thus rename to objc++ .mm files. - error: [gl] `BLOCK_SAFE_RUN` inconsistent left/right operands types this is side effect after renaming expo-gl files as .mm. fixed by explicitly cast as void. - error: [core] undefined symbols in linking time, e.g. `EXRegisterModule` this is side effect after renaming expo-gl files as .mm. fixed by export symbols by `extern "C"`, otherwise c++ will have different name mangling between c. - rename `expo-image` pod to `EXImage` - error: `Include of non-modular header inside framework module` adding `DEFINES_MODULES` for cocoapods to create modulemap file. for external dependency like firebase, ignore the error by adding `CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES` - error: expo-constant's app.config and expo-updates' app.manifest not found in use_frameworks mode, the path is the same with non framework mode. `/$UNLOCALIZED_RESOURCES_FOLDER_PATH` is unnecessary. - error: [barcode-scanner] ZXingObjC podspec GCC_PREPROCESSOR_DEFINITIONS does not export to EXBarCodeScanner and cause headers not found add these defines explicitly - [templates] add missing `react_native_post_install` from react-native 0.64 upgrade - error: `Cycle inside FBReactNativeSpec; building could produce unreliable results. This usually can be resolved by moving the shell script phase '[CP-User] Generate Specs' so that it runs before the build phase that depends on its outputs.` workaround by moving `FBReactNativeSpec` build phase script order. Co-authored-by: Tomasz Sapeta <[email protected]> # Test Plan ## prebuilt xcframework test ```sh expo init -t /path/to/expo/templates/expo-template-bare-minimum sdk43 cd sdk43 # add `s.static_framework = true` for each `node_modules/expo-*/ios/*.podspec` cd ios # add `use_frameworks!` to Podfile rm -rf Pods && pod install cd .. expo run:ios expo run:ios --configuration Release ``` ## regression for all expo-modules ```sh expo init -t /path/to/expo/templates/expo-template-bare-minimum sdk43 cd sdk43 yarn add file:/path/to/expo/packages/expo-* # add all expo-modules one-by-one # test non framework mode expo run:ios expo run:ios --configuration Release # test framework mode cd ios # add `use_frameworks!` to Podfile rm -rf Pods && pod install cd .. expo run:ios expo run:ios --configuration Release ```
Publish expo-modules-core, expo-modules-autolinking, expo[email protected][email protected][email protected]
[skip ci] move library proguard rules for ReactNative wrapper (#14407)# Why the proguard file is for `ReactNativeDelegateWrapper` and `ReactNativeHostWrapper` and now moving into expo package.
[skip ci] move library proguard rules for ReactNative wrapper (#14407)# Why the proguard file is for `ReactNativeDelegateWrapper` and `ReactNativeHostWrapper` and now moving into expo package. # How move proguard file from `@unimodules/react-native-adapter` to `expo` # Test Plan will test enabled proguard build after new bare template ready.
[ios] Bump deployment target to 12.0 (#14383)* drop ios 11 * update bare-sandbox * forgot some * add PR link to changelogs * Update packages/expo-cellular/CHANGELOG.md Co-authored-by
[ios] Bump deployment target to 12.0 (#14383)* drop ios 11 * update bare-sandbox * forgot some * add PR link to changelogs * Update packages/expo-cellular/CHANGELOG.md Co-authored-by: Expo CI <[email protected]> * et pod-install after rebase Co-authored-by: Expo CI <[email protected]>
Various cleanups in unimodules packages (#14379)
Publish packages[email protected][email protected][email protected][email protected][email protected][email protected][email protected]
Publish packages[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
Publish packages[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
Publish packages@unimodules/[email protected]@unimodules/[email protected][email protected][email protected][email protected]e
Publish packages@unimodules/[email protected]@unimodules/[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]
[packages] Migrate dependencies to expo-modules-core
[unimodules] Add deprecation notices to CHANGELOGs and READMEs (#14048)Co-authored-by: Tomasz Sapeta <[email protected]>
[ios][autolinking] Move autolinking scripts from the adapter to expo-modules-core (#14046)
[modules-core] Move js code (#13895)# Why Moves js code from `@unimodules/core` and `react-native-adapter` to `expo-modules-core` # How - Move js code. - Make sure everything is compiling
[modules-core] Move js code (#13895)# Why Moves js code from `@unimodules/core` and `react-native-adapter` to `expo-modules-core` # How - Move js code. - Make sure everything is compiling # Test Plan - bare-expo - ios ✅ - android ✅ - expo go - ios ✅ - android ✅
[sdk] upgrade typescript to v4.3.5 (#14015)
Upgrade to react native [email protected] (#13947)* [email protected] * babel upgrades * Update yarn.lock * Fixed event emitter bugs on web * Fixed GL tests * Fixed HTML tests * Up
Upgrade to react native [email protected] (#13947)* [email protected] * babel upgrades * Update yarn.lock * Fixed event emitter bugs on web * Fixed GL tests * Fixed HTML tests * Update RNWView.tsx
[unimodules] Fix `cannot find "unimodules-test-core"` (#13953)# Why Fixes `cannot find "unimodules-test-core" project`. # How Checked if `unimodules-test-core` exists before adding it to a
[unimodules] Fix `cannot find "unimodules-test-core"` (#13953)# Why Fixes `cannot find "unimodules-test-core" project`. # How Checked if `unimodules-test-core` exists before adding it to as dependence. We use tests internally, so we don't want to fail someone's build if they don't have `unimodules-test-core` installed. # Test Plan - bare-expo ✅
[ios][android] Deprecate react-native-unimodules autolinking (#13952)
[tools] Rewrite versioning expo modules (#13881)
[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
[expo-modules][android] Move autolinking.gradle to core & prevent cycle dependencies (#13753)# Why After merging `unimodules-core` & `unimodules-react-adapter`, I discovered we will have a probl
[expo-modules][android] Move autolinking.gradle to core & prevent cycle dependencies (#13753)# Why After merging `unimodules-core` & `unimodules-react-adapter`, I discovered we will have a problem with cycle dependencies. Prerequisite of https://github.com/expo/expo/pull/13703. # How - Added a new android subproject on the fly - expo-modules-linker. This project is responsible for adding all of the expo modules to the project. We can't do it in `expo-modules-core`, cause every package will eventually depend on it. What will cause cycle dependencies. The module will depend on `core` to get access to interfaces, but `core` will depend on the module to add it to the project. - Moved `auto linking` script to the `expo-module-core` # Test Plan - bare-expo - expo-go
[expo-speech] fix getting listener count (#13654)* [expo-speech] fix getting listener count * update CHANGELOG * [react-native-adapter] fix getting listener count * [react-native-adapter]
[expo-speech] fix getting listener count (#13654)* [expo-speech] fix getting listener count * update CHANGELOG * [react-native-adapter] fix getting listener count * [react-native-adapter] update CHANGELOG
[android] fix lint (#13689)
123456789