[fix][calendar] Fix iOS 17 permissions in current module (#24545)

[iOS] Fix pod install failing due to missing fields in expo-router

Exclude expo-head from Expo Go

[go] disable expo-network-addons autolinking (#23230)

# Why

currently the only feature in expo-network-addons is brotli compression for all okhttp requests. since we can literally control all okh

[go] disable expo-network-addons autolinking (#23230)

# Why

currently the only feature in expo-network-addons is brotli compression for all okhttp requests. since we can literally control all okhttp requests in expo-go, we don't this expo-network-addons in the meantime.
this may also resolve the crash issue: https://console.firebase.google.com/project/exponent-5dd6d/crashlytics/app/android:host.exp.exponent/issues/abcfcc9f22425a76b2d1170fe6463b16

# How

remove expo-network-addons from autolinking in expo-go

# Test Plan

smoke test in expo-go

show more ...

[go] add network inspector support (#22741)

# Why

add network inspector support for expo go
close ENG-8010

# How

integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo

[go] add network inspector support (#22741)

# Why

add network inspector support for expo go
close ENG-8010

# How

integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo-dev-launcher to use hacky solution, we want to enable the network inspector on release mode, so the implementation follows formal way.
- on ios, we leverage the `RCTSetCustomNSURLSessionConfigurationProvider` from react-native to create dedicated `URLSessionConfiguration`.
- on android, we already have a dedicated okhttp client from expo go. this pr just adds the interceptors.
- found image requests are not intercepted, it is because we don't use okhttp for fresco image pipeline. this pr tries to use the okhttp for fresco as react-native.
- android expo go has multiple react instances. however, the network inspector currently only support single inspector target to metro-inspector-proxy. as the result, we only limit the current foreground activity to send network inspector events.

# Test Plan

ncl + expo go to test the network inspector

show more ...

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

Make expo go work on M1 simulator (#21249)

Co-authored-by: Expo Bot <[email protected]>

Remove face detector from iOS Expo Go (#22619)

Co-authored-by: Expo Bot <[email protected]>

Remove Amplitude from Expo Go (#22523)

Introduce expo-insights module for iOS (#21932)

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

[expo-modules] Create local create-expo-module template (#21460)

[stripe] Upgrade stripe to 0.23.1 (#20964)

[expo-firebase-*] Remove libraries (#20979)

# Why

We deprecated `expo-firebase-analytics` / `expo-firebase-recaptcha` (and
hence, `expo-firebase-core`) in SDK 47, with removal planned in 48.

[expo-firebase-*] Remove libraries (#20979)

# Why

We deprecated `expo-firebase-analytics` / `expo-firebase-recaptcha` (and
hence, `expo-firebase-core`) in SDK 47, with removal planned in 48.

# How

Remove `expo-firebase-analytics`, `expo-firebase-recaptcha`,
`expo-firebase-core` packages. Updated dependencies in test apps/ Expo
Go, removed Scoped Firebase class.

Needed to update `com.google.firebase:firebase-core` to 21.1.0 in
**expoview/build.gradle** due to the below error. I think this was
related to the Expo Firebase packages requiring this version anyway,
which was likely inhibiting the error.

```
Duplicate class com.google.android.gms.internal.firebase_messaging.zza found in modules jetified-firebase-iid-20.0.2-runtime (com.google.firebase:firebase-iid:20.0.2) and jetified-firebase-messaging-22.0.0-runtime (com.google.firebase:firebase-messaging:22.0.0)
...
Duplicate class com.google.firebase.iid.FirebaseInstanceIdReceiver found in modules jetified-firebase-iid-20.0.2-runtime (com.google.firebase:firebase-iid:20.0.2) and jetified-firebase-messaging-22.0.0-runtime (com.google.firebase:firebase-messaging:22.0.0)
```

# Test Plan

Tested building bare-expo and Expo Go on iOS and Android.

# Checklist

~~**NOTE**: will open up a separate PR to update documentation; there's
a decent amount of cross-linked stuff, don't want to miss that in a
large-ish diff.~~

- [ ] 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)
- [x] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[1/3] upgrade react-native 0.71 (#20799)

# Why

upgrade react-native 0.71 for sdk 48
close ENG-7192

# How

- update package versions
- `react: 18.1.0 -> 18.2.0`
- `react-native 0.70.5

[1/3] upgrade react-native 0.71 (#20799)

# Why

upgrade react-native 0.71 for sdk 48
close ENG-7192

# How

- update package versions
- `react: 18.1.0 -> 18.2.0`
- `react-native 0.70.5 -> 0.71.0`
- `react-dom: 18.1.0 -> 18.2.0`
- `react-test-renderer: 18.1.0 -> 18.2.0`
- `react-native-web: 0.18.9 -> 0.18.10`
- `babel-plugin-react-native-web: 0.18.9 -> 0.18.10`
- `metro-react-native-babel-preset: 0.72.3 -> 0.73.5`
- upgrade three project templates based on [upgrade-helper](https://react-native-community.github.io/upgrade-helper/?from=0.70.6&to=0.71.0)
- bare-expo
- expo-template-bare-minimum
- fabric-tester (this is based on `npx expo prebuild --clean --no-install --template /path/to/expo-template-bare-minimum.tgz`) so it includes some inconsistent changes
- [@expo/config-plugins]: support 0.71 template transform. the `namespace` in build.gradle and the files in `release` build variants
- [fbjni] upgrade 0.3.0 to align 0.71 (also ndk version)
- [expo-updates] move the `EX_UPDATES_NATIVE_DEBUG` `bundleInDebug` setup to templates. unfortunately, because RNGP setups the task dependencies pretty early. the original setup in expo-updates build.gradle is too late. note that the change doesn't reference any files from templates to expo-updates package. somehow it's not tightly coupled.
- [native-tests / expo-modules-test-core / expo-modules-autolinking] fix ios unit test build error because jsc now in a dedicated podspec. in theory, the ios native unit test could now run on hermes as well.
- for other details, please check commit histories one by one.

# Test Plan

- bare-expo ios / android
- fabric ios / android
- ci passed (except ios)
- test-suite ios is broken for unknown reasons. it breaks only on github actions and hermes. for nightlies testing, i also [changed it to jsc](https://github.com/expo/expo/blob/1e029c89c4247802cc4880e27e116a6b4c71c502/tools/src/commands/SetupReactNativeNightly.ts#L287-L293) to make ci green. i'll try to follow up and investigate the root cause.

show more ...

[image][go] Add expo-image to Go (#20722)

# Why

Add `expo-image` to Expo Go ;)

[maps] Migrate code from the SWM repo (#19673)

# Why

Closes ENG-6626.
Migrates code from https://github.com/software-mansion-labs/expo-maps.

# How

- Copied library code into `packages/expo

[maps] Migrate code from the SWM repo (#19673)

# Why

Closes ENG-6626.
Migrates code from https://github.com/software-mansion-labs/expo-maps.

# How

- Copied library code into `packages/expo-maps`.
- Copied example code into `NCL`.
- Fixed problems discovered by the linter.
- Excluded google maps utils on iOS, because it didn't compile in our repo. I will investigate that in more detail later.
> Note:
To test google maps you have to add an API key to the manifest or infoplist.

# Test Plan

- bare-expo and NCL ✅

show more ...

[ios] Make expo-image an Expo module (#19435)

Update `react-native-maps` to 1.3.2 (#19414)

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

[ios][tools] Add Hermes support for Expo Go (#19078)

# Why

close ENG-6189

# How

- [tools] add *versionHermes.ts* to create a versioned hermes.xcframework. this script will be invoked in add

[ios][tools] Add Hermes support for Expo Go (#19078)

# Why

close ENG-6189

# How

- [tools] add *versionHermes.ts* to create a versioned hermes.xcframework. this script will be invoked in adding new sdk. it will also show a prompt to upload the artifact.
for ci testing, the hermes podspec also supports xcframework from local file system:

```
if File.exists?(File.join(__dir__, "destroot"))
source[:path] = '.'
else
source[:http] = 'https://github.com/expo/react-native/releases/download/sdk-47.0.0/ABI47_0_0hermes.tar.gz'
end,
```

- [tools] versioning hermes related code in react-native
- [manifest] add `jsEngine` method to read the jsEngine or ios.jsEngine value from manifest
- ~[reanimated] introduce `useHermes` runtime option to create specific js runtime~ Update: always use hermes to simplify the versioning script.
- [reanimated] backport sdk45, sdk46 code to disable hermes

# Test Plan

- `et add-sdk -p ios -s 47.0.0` + versioned expo go
- unversioned expo go + NCL
- unversioned expo go + NCL with `"jsEngine": "hermes"`
- versioning ci job passed: https://github.com/expo/expo/actions/runs/3049529467/jobs/4915687276

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

show more ...

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

[ios] Turn off signing resource bundles in Xcode 14 (#19095)

[ios] Fix mismatched Firebase versions in Expo Go (#19048)

[autolinking][ios] Add an option to include test specs from autolinked modules (#18496)

[ncl][docs][tools][expo] Remove admob, amplitude, branch, facebook-ads, facebook, google-sign-in, segment (#18168)

[expo-updates][iOS] Fix crash in Expo Go (#18056)

Why

Expo Go does not use the Expo.plist-dependent EXUpdatesService module, but relies on EXUpdatesBinding, which is loaded dynamically during the

[expo-updates][iOS] Fix crash in Expo Go (#18056)

Why

Expo Go does not use the Expo.plist-dependent EXUpdatesService module, but relies on EXUpdatesBinding, which is loaded dynamically during the React Native module loading process.

Under some circumstances (e.g. repeated reloads of the app bundle when in debug mode), it is possible to create a situation where EXUpdatesBinding is initialized too late, and the reading of module constants during load invokes EXUpdatesService.sharedInstance, triggering a crash due to Expo.plist not being present.

How

Add a new preprocessor definition (SUPPRESS_EXPO_UPDATES_SERVICE) to the Exponent Podfile post_install step, and modify EXUpdatesService so that it does not export the updates interface when present in the Expo Go app. Behavior in other apps is unaffected.

Test Plan

Manually tested to ensure that the crash is no longer reproducible.

show more ...