[ios] Migrate all remaining native code

[constants] Migrate interface to expo-modules-core (#12876)

[ios] Expo Client -> Expo Go (#10847)

The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To h

[ios] Expo Client -> Expo Go (#10847)

The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To head off confusion with default development clients, this commit renames the app store development client known as "Expo Client" to "Expo Go".

"Expo Go" is the name for the App Store and Play Store development clients that are published under the Expo team's accounts and currently have support for multiple SDK versions. Expo Go is the fastest way to get started. But we've seen billion-dollar companies use the managed workflow for production apps, so names like "Expo Lite" or "Expo Start" wrongly communicate that the app is just for demos or getting started. "Expo Go" implies it's a good way to get started and also not the entire workflow, but also a workflow that can hold its own.

In this commit I focused just on iOS (native). Android (native) and Home need to come later. I also changed "experience" to "project" in a few places to start cleaning up our terminology.

Tested by running the app and verifying it shows up as "Expo Go" on the home screen in a simulator.

show more ...

[docs][ios][local-authentication][ncl] move promptMessageIOS into option object (#4631)

# Why

Followup #4612

# How

Moved `promptMessageIOS` argument of `LocalAuthentication.authenticateAsy

[docs][ios][local-authentication][ncl] move promptMessageIOS into option object (#4631)

# Why

Followup #4612

# How

Moved `promptMessageIOS` argument of `LocalAuthentication.authenticateAsync` into the new `options` object, under `promptMessage` key.
This is a breaking change, but I hope this API will be better since this argument was required only on iOS (so it shouldn't be before options argument that is going to be used on both platform in the future).

# Test Plan

Tested on NCL example.

show more ...

[ios] Make iOS ExpoKit work without unimodules that need to be scoped (#4336)

# Why

I was unable to build a newly ejected app with ExpoKit for SDK33 without explicitly installing unimodules that

[ios] Make iOS ExpoKit work without unimodules that need to be scoped (#4336)

# Why

I was unable to build a newly ejected app with ExpoKit for SDK33 without explicitly installing unimodules that are being extended and overriden by scoped modules.

# How

Added `#if __has_include` macros to check whether the unimodule is installed before we initialize and register scoped modules.

# Test Plan

Expo Client builds, ExpoKit app without some unimodules work as expected.

show more ...

[unimodules] Remove experience references (#3993)

# Why

Properly closes https://github.com/expo/expo/pull/3875, fixes https://github.com/expo/expo/issues/3517, fixes https://github.com/expo/expo/

[unimodules] Remove experience references (#3993)

# Why

Properly closes https://github.com/expo/expo/pull/3875, fixes https://github.com/expo/expo/issues/3517, fixes https://github.com/expo/expo/issues/3864.

# How

Removed all `experience` references from universal modules, adding scoped implementations to ExpoKit.

# Test Plan

- [x] NCL works
- [x] bare template works

show more ...