Apple TV support 1: podspec and code changes for commonly used modules (#24329)# Why First of a series of PRs to add Apple TV support for many (but not all) Expo SDK modules. This PR makes A
Apple TV support 1: podspec and code changes for commonly used modules (#24329)# Why First of a series of PRs to add Apple TV support for many (but not all) Expo SDK modules. This PR makes Apple TV able to compile for apps using `[email protected]` and ONLY the following modules: - expo - expo-application - expo-constants - expo-eas-client - expo-file-system - expo-font - expo-json-utils - expo-keep-awake - expo-manifests - expo-modules-core - expo-splash-screen - expo-structured-headers - expo-updates-interface - expo-updates # How - Add tvOS to podspecs - Native code changes wrapped in `#if TARGET_OS_TV` (for Objective C) or `#if os(tvOS)` (for Swift) - Import source for the `ASN1Decoder` Swift framework used by `expo-updates`, as the public podspec for that framework does not yet support tvOS # Test Plan - Manual testing with a template still in development - Existing CI for iOS should pass (nothing should be broken) # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[expo-updates] Updates state machine for iOS and Android, E2E tests (#22845)# Why Implement state machine on Android and iOS. # How - New state machine classes on Android and iOS - Integr
[expo-updates] Updates state machine for iOS and Android, E2E tests (#22845)# Why Implement state machine on Android and iOS. # How - New state machine classes on Android and iOS - Integration with UpdatesController/AppController - State machine change events sent to JS - Test hook in `@expo/use-updates` to allow E2E tests - E2E tests for both platforms # Test Plan - Manual testing on both platforms - Unit tests for state machine on both platforms - New E2E tests for state machine feature - Existing E2E tests and existing `expo-updates` functionality should be unaffected # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
[ios] Bump deployment target to 13.0 (#18873)
[updates] Integrate ExpoReactDelegateHandler and fix bridge initialized twice issue. (#15142)# Why saving from expo-updates double bridge creation and its workaround #15019. also to keep `RCTRoo
[updates] Integrate ExpoReactDelegateHandler and fix bridge initialized twice issue. (#15142)# Why saving from expo-updates double bridge creation and its workaround #15019. also to keep `RCTRootView.initialProperties` when user in bare projects. close ENG-2299 # How - integrate with the new `ExpoReactDelegateHandler` - integrate with `EXAppDefines.APP_DEBUG`, so prebuilding `expo-updates` is possible again. # Test Plan expo init sdk43 yarn add file:/path/to/expo/packages/{expo,expo-constants,expo-modules-autolinking,expo-modules-core,expo-splash-screen,expo-status-bar,expo-updates} launch test and verify update with `expo publish` test `SplashScreen.preventAutoHideAsync()` and hide splash screen after 3s.
[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 ```
[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]>
[updates] Fix declared dependencies in expo-updates and related packages (#14362)
[ios] Migrate all remaining native code
[ios] Add dummy Swift file to native iOS tests (#13301)
[expo-structured-headers] fix wrong variable type in parser implementation (#12190)
[expo-structured-headers][expo-updates] add missing Foundation imports, fix warnings (#12175)
[expo-updates][ios] parse and persist data from EAS update headers (#11967)
[expo-structured-headers] add iOS parsing implementation and tests (#11841)
[expo-structured-headers] add empty package (#11842)