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

[android][ios] pass app.json updates config to expo-updates in standalone apps (#9985)

[ios][android][sdk][ncl] Background location, geofencing and background fetch (#2338)

# Why

Canny issues:
- https://expo.canny.io/feature-requests/p/background-tasks-support
- https://expo.cann

[ios][android][sdk][ncl] Background location, geofencing and background fetch (#2338)

# Why

Canny issues:
- https://expo.canny.io/feature-requests/p/background-tasks-support
- https://expo.canny.io/feature-requests/p/background-location-tracking
- https://expo.canny.io/feature-requests/p/geofencing-api

Related PR:
- https://github.com/expo/universe/pull/3201 (docs)

# How

The core of this PR is to implement TaskManager that provides an API to manage tasks, especially these that run while the app is in the background. I hope I documented this piece enough so I don't have to write it here again ��

This PR also adds three ways of how we can use background tasks:
- Background location updates
`Location.startLocationUpdatesAsync`, `Location.stopLocationUpdatesAsync`, `Location.hasStartedLocationUpdatesAsync`
- Geofencing
`Location.startGeofencingAsync`, `Location.stopGeofencingAsync`, `Location.hasStartedGeofencingAsync`
- Background fetch
`expo-background-fetch` module, *iOS only so far*

Also, to improve the quality of `expo-location`, I've deprecated `enableHighAccuracy` option and introduced a new one called `accuracy`. It allows to use all possible accuracies provided by iOS platform. Android has fewer options of accuracy, but I've made simple mapping (see https://github.com/expo/expo/pull/2338/files#diff-66bdbbc66d3410d9198aa17584b5409eR633).

All new modules and `expo-location` are now TypeScripted ��

# Test Plan

New APIs examples in `native-component-list`:
- `BackgroundFetch` - shows the status and the date of the last background fetch which can be manually triggered in Xcode (Debug -> Simulate background fetch).
- `Location` -> `Background location map` - it tracks your location by drawing a polyline.
- `Location` -> `Geofencing map` - this one will work better once we merge #2316, as it should show local notifications when the device enters/exits a region.
- `TaskManager` - shows all registered tasks for the experience.

There are also some quick tests in `test-suite` for the new methods in `Location` and `TaskManager` modules.

show more ...

[android][ios][home] persist session info in one location on clients (#2521)

[android][ios][home][jest-expo] persist session info in one location on clients

[android][ios][home] send the sessionSecret along with manifest requests in the expo client (#2503)

Clean up EXEnvironment, remove deprecated shell development config behavior

fbshipit-source-id: f4d4d01

Remove deprecated flag that allowed old standalone apps to skip the splash API

fbshipit-source-id: d49d57d

Remove isShell property because it is now identical to isDetached

Also clean up a few other props that had shell in the name

closes https://github.com/expo/universe/issues/2460

fbshipit-source-id:

Remove isShell property because it is now identical to isDetached

Also clean up a few other props that had shell in the name

closes https://github.com/expo/universe/issues/2460

fbshipit-source-id: fac520e

show more ...

EXShellManager -> EXEnvironment

fbshipit-source-id: 2347314