[github] Fix stale issue message
[pr-labeler] remove debug log that would terminate the action
[pr-labeler] fix fingerprint output and labeling
[pr-labeler] fix working directory
[ci] add pr-label by fingerprint (#24550)# Why dogfooding fingerprint # How add a pr-babeler for test-suite to check fingerprint compatibility
Apple TV support 2: add TV template, fix config plugin, add CI (#24411)
split create-expo tests out of Expo CLI tests (#24456)# Why Keep the Expo CLI tests fast
chore(create-expo): move package from `expo/expo-cli` to `expo/expo` (#24373)# Why Moving this actively used/developed package from [expo/expo-cli](https://github.com/expo/expo-cli) to [expo/e
chore(create-expo): move package from `expo/expo-cli` to `expo/expo` (#24373)# Why Moving this actively used/developed package from [expo/expo-cli](https://github.com/expo/expo-cli) to [expo/expo](https://github.com/expo/expo). > ⚠️ ~~Blocked by `@expo/package-manager` changes being merged only in `sdk-49` and not `main`. See https://github.com/expo/expo/pull/24376~~ > Merged in this PR! # How - Copied project into **packages/create-expo-app** - Applied various changes to fit it in the repository # Test Plan See CI # 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[docs] Remove `expo-dict.json` & case-police (#24270)
[home][ci] Remove dogfood expo home variant (#24193)
[ci][tools] fix react-native 0.73 compatibility [3/3] (#24020)# Why fix react-native 0.73 compatibility. this pr focus on fixing ci test-suite-nightlies. # How - [ci] use node 18 and jdk 1
[ci][tools] fix react-native 0.73 compatibility [3/3] (#24020)# Why fix react-native 0.73 compatibility. this pr focus on fixing ci test-suite-nightlies. # How - [ci] use node 18 and jdk 17 which are required from 0.73 - [ci] use `npx pod-install` rather than `pod install` and fix hermes-engine podfile.lock update issue - [tools] update SetupReactNativeNightly script # Test Plan ci passed in #23961 (https://github.com/expo/expo/pull/23961/checks)
[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
chore: improve expo router testing (#23795)# Why - Ensure the various aspects of `npx expo export` continue to work with the latest Expo Router/Metro depdencies. - We had a bundling testing fo
chore: improve expo router testing (#23795)# Why - Ensure the various aspects of `npx expo export` continue to work with the latest Expo Router/Metro depdencies. - We had a bundling testing for Expo Router but it wasn't linked to the monorepo so the dependencies weren't in sync. <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> # How - Create a new app in `apps/` which is synchronized with the monorepo. - This app contains multiple expo-router directories and various dynamic settings. - Fold the `expo-router` e2e tests into `@expo/cli`. - Test static rendering, single-page application exporting, and the native url polyfill (api). <!-- How did you build this feature or fix this bug and why? --> # Test Plan - The CLI E2E tests should pass. --------- Co-authored-by: Expo Bot <[email protected]>
[go][sqlite] fix broken state for ios expo go (#23885)# Why ios expo-go has a couple error in the mean time, this pr is to address them all. # How - `pod install` error: outdated podfile.l
[go][sqlite] fix broken state for ios expo go (#23885)# Why ios expo-go has a couple error in the mean time, this pr is to address them all. # How - `pod install` error: outdated podfile.lock since #23858 - build error from sqlite, since expo-go mixes ios builtin sqlite3 and community sqlite3. for example, sqlite3 `create_filename` is different. we should use older sqlite3 to make sure everything is compatible. - `char *(*create_filename)(const char*,const char*,const char*, int,const char**);` - `const char *(*create_filename)(const char*,const char*,const char*, int,const char**);` - missing some files to build for versioned expo-go, when testing with versioned expo-go. it will have runtime error because of missing modules. # Test Plan - ci passed - versioned expo go + NCL `EXPO_SDK_VERSION=UNVERSIONED npx expo start`
[docs] Adds docs preview label (#20583)# Why We'd like the ability to add a label, then to have GitHub Actions build the docs and deploy them on AWS S3, where we can preview them quickly durin
[docs] Adds docs preview label (#20583)# Why We'd like the ability to add a label, then to have GitHub Actions build the docs and deploy them on AWS S3, where we can preview them quickly during PR review. This PR adds a GitHub Action (GHA) that gets triggered when added the "preview" label. The GHA exports/builds the docs and then uploads them to AWS S3. Then, it comments on the PR with a link to the preview URL. When merging a PR, another GHA runs to clean up and delete the bucket that was created when adding the label. Closes ENG-5683 # How - Added a `AWS_BUCKET` field to our **deploy.sh** to specify the bucket to deploy to. - Edits the search inside the docs to replace `docs.expo.dev` with the preview URL if the docs are hosted on an aws-style URL. # Test plan You should see the docs preview website on this PR! Go check it out. Also, I opened another PR on top of this one where I confirmed both pr-deploy and pr-destroy steps (on label add, remove, and merge). See the screenshots in the comments on this PR: https://github.com/expo/expo/pull/23545
Remove unneeded .ruby-version file (#23237)
[ci] trying to fix flaky ios unit test ci (#23245)# Why flaky ios unit test ci from timeout: https://github.com/expo/expo/actions/runs/5427238787/jobs/9870870707 # How - use macos 13 - us
[ci] trying to fix flaky ios unit test ci (#23245)# Why flaky ios unit test ci from timeout: https://github.com/expo/expo/actions/runs/5427238787/jobs/9870870707 # How - use macos 13 - use xcode 14.3 - use iphone 14 pro simulator for unit tests though it still having timeout, be seems better without exceeding the 24s timeout
[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`
[cli] fix typecheck from react-native 0.72 upgrade (#22766)# Why follow up #22588 which disabled the cli typecheck # How using types from metro and fix typing issues # Test Plan cli
[cli] fix typecheck from react-native 0.72 upgrade (#22766)# Why follow up #22588 which disabled the cli typecheck # How using types from metro and fix typing issues # Test Plan cli ci passed
Update SwiftLint to 0.52.2 (#22801)
[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
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]>
[github] Add react-native-core invalid issue label (#22627)# Why Adding a new `invalid issue: react-native-core` label should help us closing issues that are related to the react-native-core
[github] Add react-native-core invalid issue label (#22627)# Why Adding a new `invalid issue: react-native-core` label should help us closing issues that are related to the react-native-core # How Add a new `invalid issue: react-native-core` label and bot comment # Test Plan N / A # 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Brent Vatne <[email protected]>
[ci] add retries for test-suite android-test (#22298)# Why android emulator on github actions is occasionally flaky. # How retry three times for the use-android-emulator action. the main
[ci] add retries for test-suite android-test (#22298)# Why android emulator on github actions is occasionally flaky. # How retry three times for the use-android-emulator action. the main idea is `continue-on-error: true` and `if: steps.retries-n.outcome == 'failure'` # Test Plan ci passed (though i does not get a chance to repro the flaky emulator. let's ship it and see)
[et] commands for build and submitting Expo Go using EAS (#22194)
12345678910>>...14