[expo-updates-interface][ios] convert to swift (#21646)# Why More swift conversions. # How Convert manually. # Test Plan Run all tests. # Checklist <!-- Please check the appro
[expo-updates-interface][ios] convert to swift (#21646)# Why More swift conversions. # How Convert manually. # Test Plan Run all tests. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[exupdates][ios] Convert controllers to swift (#21591)# Why This converts the entry points (controllers) to swift. # How Convert manually # Test Plan Build and run expo go, run all t
[exupdates][ios] Convert controllers to swift (#21591)# Why This converts the entry points (controllers) to swift. # How Convert manually # Test Plan Build and run expo go, run all tests. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[expo-updates][iOS] Get downloaded update IDs (#17817)Why In order for the dev client to be able to indicate in the UI whether a particular update is available to load offline, we need to add a
[expo-updates][iOS] Get downloaded update IDs (#17817)Why In order for the dev client to be able to indicate in the UI whether a particular update is available to load offline, we need to add a method to the expo-updates-interface to let it see which updates are stored locally (in sqlite) and ready to load. It should be sufficient for this method to return a list of UUIDs for updates that have the READY status in sqlite. How New method ```objc - (void)storedUpdateIdsWithConfiguration:(NSDictionary *)configuration success:(EXUpdatesQuerySuccessBlock)successBlock error:(EXUpdatesErrorBlock)errorBlock; ``` is added to the interface for iOS. The implementation in `EXUpdatesDevLauncherController` calls into a new method in `EXUpdatesAppLauncherWithDatabase`, which uses a new query in `EXUpdatesDatabase` to retrieve READY update UUIDs. Test Plan New unit tests are added to the existing `EXUpdatesAppLauncherWithDatabaseTests` to verify the changes.
[updates-interface][updates][dev-launcher] add EXUpdatesControllerRegistry (#16230)
[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 ```
[expo-dev-launcher][expo-updates] reset updates module state on each load (#13346)
[expo-updates-interface] rename iOS protocol to EXUpdatesExternalInterface (#13214)
[expo-updates-interface] make Update nullable in onSuccess callback (#13136)
[expo-updates-interface][ios] add podspec and EXUpdatesInterface protocol (#13088)# Why iOS counterpart to #13030. Will add Manifest types in a separate later PR, same as Android # How - a
[expo-updates-interface][ios] add podspec and EXUpdatesInterface protocol (#13088)# Why iOS counterpart to #13030. Will add Manifest types in a separate later PR, same as Android # How - add protocol and podspec - rename expo-updates' internal EXUpdatesInterface to EXUpdatesModuleInterface to prevent class name collision # Test Plan manual tests in later PRs # Checklist - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.io and README.md). - [x] This diff will work correctly for `expo build` (eg: updated `@expo/xdl`). - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).