[ci] try to improve ci stability (#24002)

# Why

try to improve ci stability

# How

- android-unit-tests
- prevent timeout and out of disk space
- client-android-eas
- since client-and

[ci] try to improve ci stability (#24002)

# Why

try to improve ci stability

# How

- android-unit-tests
- prevent timeout and out of disk space
- client-android-eas
- since client-android is not stable, try to broad the client-android-eas path coverage
- for external contributors (forked repo), just ignore the workflow
- client-ios-eas
- for external contributors (forked repo), just ignore the workflow
- client-android
- TBD
- client-ios
- remove s3 and store publish
- ios-unit-tests
- prevent timeout
- clipboard
- fix timeout issue because of slow NSAttributedString html processing
- `et dispatch`: remove unused workflows
- releasing guide: update to the newer `et eas` releasing workflows

# Test Plan

ci passed

show more ...

Remove unneeded .ruby-version file (#23237)

[go] fix crashlytics gradle plugin build error (#23139)

# Why

building error for `./gradlew :app:assembleVersionedRelease`

```
FAILURE: Build failed with an exception.

* What went wrong:

[go] fix crashlytics gradle plugin build error (#23139)

# Why

building error for `./gradlew :app:assembleVersionedRelease`

```
FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':app:mergeVersionedReleaseNativeLibs' (type 'MergeNativeLibsTask').
- Gradle detected a problem with the following location: '/Users/kudo/01_Work/Repos/expo/expo/android/app/build/intermediates/merged_native_libs/versionedRelease/out'.

Reason: Task ':app:injectCrashlyticsBuildIdsVersionedRelease' uses this output of task ':app:mergeVersionedReleaseNativeLibs' without declaring an explicit or implicit dependency. This can lead to incorrect
results being produced, depending on what order the tasks are executed.

Possible solutions:
1. Declare task ':app:mergeVersionedReleaseNativeLibs' as an input of ':app:injectCrashlyticsBuildIdsVersionedRelease'.
2. Declare an explicit dependency on ':app:mergeVersionedReleaseNativeLibs' from ':app:injectCrashlyticsBuildIdsVersionedRelease' using Task#dependsOn.
3. Declare an explicit dependency on ':app:mergeVersionedReleaseNativeLibs' from ':app:injectCrashlyticsBuildIdsVersionedRelease' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
```

# How

- upgrade crashlytics gradle plugin. this issue probably relate to this: https://github.com/firebase/firebase-android-sdk/issues/4682
- since this pr touches `android/build.gradle`, it will trigger ci for building versioned expo-go and suffered from the error of "no space left" on github ci. i've tried to address the problem by some changes:
- only upload crashlytics on eas build
- add a composite github action to cleanup github linux runner disk space

# Test Plan

- ci passed
- `./gradlew :app:assembleVersionedRelease`

show more ...

[ci] use ubuntu-22.04 runner (#22797)

# Why

use the latest ubuntu runner and make ci more stable

# How

update to ubuntu-22.04 runner

[core] Added `REACT_NATIVE_DOWNLOADS_DIR` environment variable support (#19015)

# Why

it's not ideal for an app to download 3rd party libraries multiple times.

# How

- [core][expoview] add

[core] Added `REACT_NATIVE_DOWNLOADS_DIR` environment variable support (#19015)

# Why

it's not ideal for an app to download 3rd party libraries multiple times.

# How

- [core][expoview] add `REACT_NATIVE_DOWNLOADS_DIR` environment variable to support custom download location. the way is aligned with [react-native](https://github.com/facebook/react-native/blob/37d0a25cb28879449d89056079c94177c7d2c73f/ReactAndroid/build.gradle#L34-L35)
- [ci] add `react-native-gradle-downloads` expo cache to set the `REACT_NATIVE_DOWNLOADS_DIR` variable and restore the cache from `$HOME/.gradle/react-native-downloads`. note that i've set the cache key as yarn.lock hash value, because GH cache action will not store the updates to storage as long as cache hit. we should use a new key after dependencies changes after react-native upgrade.

# Test Plan

- `REACT_NATIVE_DOWNLOADS_DIR=$HOME/foo ./gradlew :app:assembleDebug` in apps/bare-expo/android and verify the download files should present in $HOME/foo
- ci passed and once `react-native-gradle-downloads` cache hit, the downloadBoost task should not download the boost library.

show more ...

[github] try to fix client android ci error

[CI] Fix android ci failures (#18370)

# Why

fix android client and instrumented test ci failures

# How

- android client: reduce jvm usage a little bit to prevent OOM be killed by github run

[CI] Fix android ci failures (#18370)

# Why

fix android client and instrumented test ci failures

# How

- android client: reduce jvm usage a little bit to prevent OOM be killed by github runners.
- android instrumented test: it loooks like timeout and emulator disk size is not enough

# Test Plan

ci passed

show more ...

[ci] fix android client building OOM

[ios] Update react-native to 0.69 for expo go (#17629)

# Why

upgrade react-native for sdk 46

# How

- update our react-native fork
- [android] add hermes-engine prebuilding. the main change

[ios] Update react-native to 0.69 for expo go (#17629)

# Why

upgrade react-native for sdk 46

# How

- update our react-native fork
- [android] add hermes-engine prebuilding. the main change is [here](https://github.com/expo/react-native/commit/8bb810c9860fc1e49d9f55bb3929ad0eb534f441). because in expo-go we are building react-native from source. in 0.69 it also means to build hermes from source. that will make our ci time more difficult.
- [expo][android] add ReactNativeHostWrapper for 0.69 because `com.facebook.react.devsupport.interfaces.RedBoxHandler` package renaming.
- update some expo modules to support 0.69

**TODO**
`et update-rn` is not included in this pr. i will do it later and commit directly. because that includes mass changes and makes review very difficult.

# Test Plan

update react-native, react, in expo/expo and test NCL with android/ios unversioned expo go

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

show more ...

[github] add local composite actions for CI, refactor workflows (#17162)

Revert "[github] Attempt to switch Android client workflow to mac temporarily [skip ci]"

This reverts commit ef4ba76c35569ace95faf7dfb85931233124e020.

[github] Attempt to switch Android client workflow to mac temporarily [skip ci]

[github] remove `@unimodules` directory from cache paths (#17139)

[github] fix docs deploy and other AWS related workflows (#17077)

[github] always use `ubuntu-20.04` in workflows (#17051)

[github] update most of GitHub actions used in workflows (#17003)

[android][ios] Upgrade expo go to react-native 0.68 (#16752)

# Why

upgrade for sdk 45

# How

- upgrade our react-native fork to 0.68 based: https://github.com/expo/react-native/tree/sdk-45

[android][ios] Upgrade expo go to react-native 0.68 (#16752)

# Why

upgrade for sdk 45

# How

- upgrade our react-native fork to 0.68 based: https://github.com/expo/react-native/tree/sdk-45
- migrate android/ios projects to 0.68
- [android] bump `targetSdkVersion` and `compileSdkVersion` to 31 (aligned with react-native 0.68)
- [tools] update codegen customization in `update-rn` script
- [tools] update versioning scripts
- [android] replace our customized `NDK_ABI_FILTERS` with official supported `reactNativeArchitectures` gradle property
- [android] use jdk 11

that is a huge pr because of changes from `et update-rn`. recommend to review this pr by commits.

most `add-sdk` problems on 0.68 are fixed. there are still an issue on android. i'll address in another pr.

- expo-av CMakeLists.txt versioning

# Test Plan

- unversoned android expo-go + ncl
- unversoned ios expo-go + ncl
- `et add-sdk -p ios -s 45.0.0` + versioned ios sdk 45 expo-go + ncl
- `et add-sdk -p android -s 45.0.0` + versioned android sdk 45 expo-go + ncl (should commented out expo-av in `ExperiencePackagePicker.kt`

show more ...

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* f

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* fix e2e tests

* lint before build

* use mock version

show more ...

[android][ios] Upgrade react-native to 0.67.2 in Expo Go (#16400)

# Why

upgrade for sdk 45

# How

## upgrade react native fork

code in https://github.com/expo/react-native/tree/sdk-45
ba

[android][ios] Upgrade react-native to 0.67.2 in Expo Go (#16400)

# Why

upgrade for sdk 45

# How

## upgrade react native fork

code in https://github.com/expo/react-native/tree/sdk-45
basically cherry pick most necessary commits from sdk-44 branch but not these two:

1. https://github.com/expo/react-native/commit/125b36ac6d76e702bea4d7c41a8a402d68cdb1f1: because ExpoKit is already deprecated.
2. https://github.com/expo/react-native/commit/82d3ff5218cc576b5c7ea44c7adbf8b5aa5d985c: [use the official way to set metro server address](https://github.com/facebook/react-native/commit/e2b5b6504cb4dee8f2ec67f1d3a410801e1ca09a)

## migrate project setup

basically reference from: https://react-native-community.github.io/upgrade-helper/?from=0.64.2&to=0.67.2

## other build errors or launch errors

just to deal with these mess one by one.

# Test Plan

- [android] unversioned expo-go build + launch + load unversioned NCL
- [ios] unversioned expo-go build + launch + load unversioned NCL

show more ...

[fastlane] Use aab for Expo Go for Android (#15602)

[github] Update default branch to main

[ci] Update Slack channels in workflows [skip ci]

[client-android] Attempt to fix unresolved fastlane binary in job

[ci] Fix sheduled client build (#13408)

* [ci] Fix sheduled client build

[CI] Schedule versioned Expo Go builds (#13377)

* Schedule versioned android client build

* Add missing CI step

* Schedule iOS client build