[go] Load embedded bundle and manifest in release builds (#24412)

[tools] Switch expo home publishing to EAS update (#24216)

[home][ci] Remove dogfood expo home variant (#24193)

[iOS] Refactor version manager in Expo Go (#23624)

[exupdates][ios] Start converting to swift (#21320)

# Why

Start the conversion process of the expo-updates library by converting
EXUpdatesUpdate and subclasses.

# How

Convert manually... l

[exupdates][ios] Start converting to swift (#21320)

# Why

Start the conversion process of the expo-updates library by converting
EXUpdatesUpdate and subclasses.

# How

Convert manually... lol.

The main note is that we can't use swift nullability/type forcing
operators (`!`, `as!`, `as?`) etc since the previous implementation was
relying upon NSAssert to raise an NSException which is caught in the
calling code, so I added new extension functions to replicate the
behavior (similar to EXManifests util functions).

# Test Plan

Build and run all tests.

# 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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[exmanifests][ios] Convert to swift (#21298)

[Expo Go][iOS] No remote home app loads in release builds (#20416)

# Why

Per ENG-7047, we need to disable remote loading of home app, and
checking for home app updates, for release builds.
Upda

[Expo Go][iOS] No remote home app loads in release builds (#20416)

# Why

Per ENG-7047, we need to disable remote loading of home app, and
checking for home app updates, for release builds.
Updates and loading from the packager will still work in debug builds.

# How

Add `#ifdef DEBUG` in several places in
`Exponent/Kernel/AppLoader/EXAppLoader.m`

# Test Plan

- CI should pass
- Test Expo Go builds locally and verify that updates are not loaded,
and that nothing else is 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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[expo-manifests][android] Move factory into package (#14273)

[expo-manifests] Rename RawManifest -> Manifest (#14194)

[expo-updates] Factor out raw manifests into their own package (#14183)

[actions] Run dogfooding home kernel publish before building client (#13960)

[ios] Use stable manifest ID where applicable (#13280)

[ios] Merge unimodules core and adapter into expo-modules-core (#13353)

# Why

Part of Expo modules re-architecture

# How

- Copied iOS sources from `@unimodules/core` and `@unimodules/react-

[ios] Merge unimodules core and adapter into expo-modules-core (#13353)

# Why

Part of Expo modules re-architecture

# How

- Copied iOS sources from `@unimodules/core` and `@unimodules/react-native-adapter` to `expo-modules-core`
- In these copied files replaced `UM` prefix with `EX`
- Swift names for classes used by the users (`AppDelegateWrapper`, `ModuleRegistry`, `ModuleRegistryAdapter`, `ModuleRegistryProvider`) won't have any prefix — we would drop these prefixes anyway, in the future when we rewrite them to Swift
- Old `UM*` names are still supported and most of them are marked as deprecated, however I couldn't get it to work for Swift (but seems like no one uses it for app delegates?) and protocols
- `ExpoModulesCore` provides `EXUnimodulesCompat.h` header that expands old `UM_*` macros to `EX_*`
- Previously `ExpoModulesCore` depended upon `UMCore`, now it's the other way around — `UMReactNativeAdapter` and `UMCore` depend on `ExpoModulesCore` to import `EXUnimodulesCompat` header
- Fixed `EXTrackingTransparency` to depend on `ExpoModulesCore` directly
- _There are no changes in the logic or architecture of unimodules/expo modules, I'll do this separately_

# Test Plan

- CI jobs are passing
- Tested locally, apps seem to work as before

show more ...

[go][ios][android] Fix recent project feature with new manifest wrappers (#12805)

[updates] Factor out raw manifest into wrapper class (#12631)

[expo-constants] add executionEnvironment (#10986)

[ios] Extract filesystem directories generation to app manager (#9676)

# Why

When TurboModules are enabled we'll need to have access to `documentDirectory` from within instance scope of `EXVersio

[ios] Extract filesystem directories generation to app manager (#9676)

# Why

When TurboModules are enabled we'll need to have access to `documentDirectory` from within instance scope of `EXVersionManager` to be able to create `RCTAsyncLocalStorage` on demand. Right now we're fetching the directory from an instance of `EXFileSystem`. Moving it higher up makes sense not only for this purpose, but also it fits well logically — the manager knows where the app should store files, not the module.

# How

Moved the generation of `documentDirectory` and `cachesDirectory` from `EXScopedFileSystemModule` to `EXReactAppManager`. Added the directories to `NSDictionary *params` passed to `EXVersionManager` (and then to `EXScopedModuleRegistryAdapter`). Moved the initialization logic from scoped module to adapter (whether the module should be created with custom directories or with default directories depends now on whether the directory paths have been provided, which still depends on the same `appOwnership == "expo"` condition.

# Test Plan

Expo Client ran. I've also verified with native debugging that Home gets the scoped directories.

show more ...

[ios] Make VersionManager remember extra params (#9682)

# Why

We need to be able to access `params` in an instance method other than `extraModulesWithParams:` for TurboModules support.

# How

[ios] Make VersionManager remember extra params (#9682)

# Why

We need to be able to access `params` in an instance method other than `extraModulesWithParams:` for TurboModules support.

# How

Since the params don't change I moved them to an instance method of app manager which passes them to `EXVersionManager`s when creating them.

# Test Plan

Expo Client compiled and ran Snacks of different SDK versions without problems.

show more ...

[ios][et] Remove Fabric and Crashlytics on iOS (#8160)

# Why

Part of #8047 - not closing yet because I'm gonna make separate PR for Android.

# How

I removed:
- Fabric and Crashlytics from

[ios][et] Remove Fabric and Crashlytics on iOS (#8160)

# Why

Part of #8047 - not closing yet because I'm gonna make separate PR for Android.

# How

I removed:
- Fabric and Crashlytics from `Podfile` and run `pod install`.
- code calling Fabric & Crashlytics libraries.
- `et ios-run-fabric` command and its `run-fabric.sh` build phase in general.
- modifying `Info.plist` while generating dynamic macros, it was used only to apply fabric's api key.
- `et ios-cleanup-dynamic-macros` command - no longer needed if we don't modify `Info.plist`.
- Fabric's key from `Info.plist`.

## Side notes

Previously, once Crashlytics detects a crash, we set a flag in user defaults and then if that flag is set we invalidated cached kernel's bundle. After these changes, kernel's bundle won't be invalidated. I chatted with James and he agrees that we actually don't need this anymore.

# Test Plan

Xcode project builds and works as expected.

show more ...

[constants] make installationId available in bare (#6906)

* [constants] make available in bare

* make filename constant

* remove installationId from scoped android module

* remove installat

[constants] make installationId available in bare (#6906)

* [constants] make available in bare

* make filename constant

* remove installationId from scoped android module

* remove installationId from scoped ios

* fix ios_test_suite

show more ...

[ios][expotools] Fix iOS versioning (#4900)

# Why

Fixes several issues I've encountered while versioning iOS code for SDK34.

# How

- Fixed `EXVersions.h` being imported in versioned code.

[ios][expotools] Fix iOS versioning (#4900)

# Why

Fixes several issues I've encountered while versioning iOS code for SDK34.

# How

- Fixed `EXVersions.h` being imported in versioned code.
- Fixed `jsireact` versioning, it's prefixed now.
- Removed versioned pods that were originally excluded from the client.
- Added post-transform prefixing `SimAnimationDragCoefficient` in `react-native-reanimated`.

# Test Plan

Expo client builds fine after versioning.

show more ...

[packages] Move unimodules foundation to `org.unimodules` scope

[ios][home] remove deprecated client-side authentication checks for opening projects

[home][ios] add diagnostics screen with background location demos (#3194)

* [home] add diagnostics screen

* [ios] fix home not having experienceUrl in constants

* [home] make background locati

[home][ios] add diagnostics screen with background location demos (#3194)

* [home] add diagnostics screen

* [ios] fix home not having experienceUrl in constants

* [home] make background location diagnostic screen look better

* [ios] fix notification events not being send to home experience

* [home] add diagnostic screen for geofencing

* [home] subtle changes in background location diagnostic screen

* [home] Only show diagnostics screen on iOS for now

* [home] Verify permissions and handle the case where they are rejected

show more ...

allow selfhosted apps to be opened in iOS home (#3028)

fbshipit-source-id: 8dcd86a