History log of /expo/packages/expo-splash-screen/ios/EXSplashScreen.podspec (Results 1 – 12 of 12)
Revision Date Author Comments
# ef901781 11-Sep-2023 Douglas Lowder <[email protected]>

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 ...


# c0a96678 07-Jun-2023 Kudo Chien <[email protected]>

Upgrade react-native 0.72.0-rc.5 (#22588)

# Why

upgrade react-native 0.72 for sdk 49
close ENG-8011

# How

- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-reac

Upgrade react-native 0.72.0-rc.5 (#22588)

# Why

upgrade react-native 0.72 for sdk 49
close ENG-8011

# How

- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-react-native-babel-preset 0.73.9 -> 0.76.5`
- [bare-expo][templates][fabric-tester] migrate template base on [upgrade-helper](https://react-native-community.github.io/upgrade-helper/?from=0.71.7&to=0.72.0-rc.5)
- [expo-template-tabs] remove the metro version overrides for expo-router.
- [core][dev-laucher][dev-menu][media-library][screen-orientation][splash-screen][updates-interface][updates] add the `install_modules_dependencies` to support new architecture + use_frameworks!
- [core][autolinking] fix some new architecture error on ios
- [react-native-lab] update our fork to 0.72.0-rc.5 based
- [go][tools] fix **react-native-lab/react-native/packages/react-native** path move because of react-native's repo monorepo changes
- [go][android] fix gradle 8 errors
- [go][ios] add `RCT_REMOTE_PROFILE=0` to fix the `RCT_ENABLE_INSPECTOR needs to be set to fulfill RCT_REMOTE_PROFILE` build error
- [ncl] remove `ProgressViewIOS` / `ProgressBarAndroid` since they are deprecated/removed in 0.72
- [dev-menu][dev-launcher] rebuild bundles

# Note

- react-native-web is not bumped because of the [issue](https://github.com/necolas/react-native-web/issues/2523), so it's still react-native-web@~0.18.10.
- currently disable ci typecheck for @expo/cli because of upstream metro typescript support. i'll have another pr to fix those errors.
- updates e2e ci on android is broken at [here](https://github.com/expo/expo/blob/fada3d764957779fbfc3d7b723d185db1d933d95/packages/expo-updates/e2e/fixtures/Updates.e2e.ts#L518). i doubt if that's related to the react scheduler change. i'd disabled the failed test case.
- the react-native upstream [migrated away the `@types/jest`](https://github.com/facebook/react-native/pull/36068). i was afraid that will be a breaking change to the existing jest test code since it requires the explicit `@jest/globals` import. i didn't do this in this upgrade.

# Test Plan

- ✅ fabric-tester (without expo-dev-client)
- ✅ ci passed. there are some errors which are known:
- updates e2e on android: as mentioned above
- ios expo go on eas build: versioned expo go are broken on eas build m1 worker. this is also happening on main.
- android client: no space left on the ubuntu worker. this is also happening on main.
- ✅ bare-expo
- ✅ unversioned expo go + ncl

---------

Co-authored-by: Tomasz Sapeta <[email protected]>

show more ...


# c88b85cf 14-Sep-2022 Tomasz Sapeta <[email protected]>

[ios] Bump deployment target to 13.0 (#18873)


# 9886c0aa 28-Sep-2021 Kudo Chien <[email protected]>

[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
```

show more ...


# 71ebd28e 13-Sep-2021 Charlie Cruzan <[email protected]>

[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]>

show more ...


# efd75dec 16-Aug-2021 Tomasz Sapeta <[email protected]>

[ios] Migrate all remaining native code


# 089a3d82 15-Dec-2020 Tomasz Sapeta <[email protected]>

[ios] Bump deployment target to iOS 11.0 (#11344)


# 52a1f6d0 04-Dec-2020 Tomasz Sapeta <[email protected]>

[ios] Require CocoaPods >=1.10.0 to use prebuilt libraries
Before v1.10.0 binaries built for arm64 simulator were treated as the ones for the device and so the build fails at linking.


# 6e1dd0e8 02-Dec-2020 Tomasz Sapeta <[email protected]>

[ios] Make podspecs compatible with prebuilds (#11183)


# 25be6b63 17-Nov-2020 Bartłomiej Bukowski <[email protected]>

[branch][image][media-library][random][splash-screen][updates][Expo][iOS] Change 'React' dependency to 'React-Core' (#11057)

Co-authored-by: Brent Vatne <[email protected]>


# 4774949e 14-Jul-2020 Bartłomiej Bukowski <[email protected]>

[splash-screen][iOS] Remove flicker in-between Splash & ReactApp (#8739)

Fixed flicker in-between SplashScreen and ReactApp phases on iOS


# 94cbc77e 25-Mar-2020 Bartłomiej Bukowski <[email protected]>

[splash-screen][bare][iOS][Android] Create expo-splash-screen (#7066)

* [splash-screen][bare][Android] Create splash screen mechanism

Unimodule features on Android:
- SplashScreen is mounted un

[splash-screen][bare][iOS][Android] Create expo-splash-screen (#7066)

* [splash-screen][bare][Android] Create splash screen mechanism

Unimodule features on Android:
- SplashScreen is mounted under ContentView
- SplashScreen's image & backgroundColor are configurable
- SplashScreen would automatically hide when view hierarchy is mounted in located RootView
- SplashScreen would appear again when RootView has no children again ('reload' behaviour from react-native)

* [splash-screnn][bare][iOS][Android] Create unimodule from template

* [splash-screen][bare][iOS] Create splash screen mechanism

Unimodule features on iOS:
- SplashScreen is mounted per ViewController
- SplashScreen's image & backgroundColor are configurable via .sotryboard file
- SplashScreen would automatically hide when ContentDidAppear notification is published
- SplashScreen would appear again when bridge is reloaded ('reload' behaviour from react-native)

* [splash-screen][Android] Adjust PR according to comments

* [splash-screen][Android][docs] Adjust PR according to comments and concerns & provide documentation for Android

* [splash-screen][iOS] Adjust PR according to comments

* [splash-screen][iOS][docs] Provide installation and configuration instructions

* [splash-screen][iOS] Restore unintetionally deleted SplashScreenView creation

* [splash-screen][iOS][Android][docs] Apply PR suggestions

* [splash-screen][iOS][Android] Make 'preventAutoHide' and 'hide' methods idempotent

* [splash-screen][Android] Exclude from Expoview

* [splash-screen][docs] Adjust docs according to PR suggestions

* [splash-screen][bare-expo] Ignore splash-screen package in bare-expo

* [splash-screen] Change version to 0.1.0

show more ...