[ios] Remove dead code (#24316)
[tools] Switch expo home publishing to EAS update (#24216)
[home][ci] Remove dogfood expo home variant (#24193)
Remove Amplitude from Expo Go (#22523)
[expo-updates][expo-go] Support new SDK version field in new manifests (#22356)
[exmanifests][ios] Convert to swift (#21298)
[expo-manifests] Rename RawManifest -> Manifest (#14194)
[expo-updates] Factor out raw manifests into their own package (#14183)
[client] Add dogfood home build option (#13883)
[ios] Split Expo Go to unversioned and versioned flavors (#11999)
[updates] Factor out raw manifest into wrapper class (#12631)
[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 ...
[ios] fix fallbackToCacheTimeout logic from EXShell (#10129)
[android][ios] pass app.json updates config to expo-updates in standalone apps (#9985)
[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.
[expo-application] Add methods for app release type and APNs environment (#6724)# Why APNs environment will be useful for `expo-notifications` module. App release type could be useful for users'
[expo-application] Add methods for app release type and APNs environment (#6724)# Why APNs environment will be useful for `expo-notifications` module. App release type could be useful for users' analytics. # How In the gist of things, I moved `EXProvisioningProfile` from `ExpoKit` to `EXApplication`. Kernel either uses `EXApplication/EXProvisioningProfile` (if it's present) or uses sensible fallback values. # Test Plan Added tests to `test-suite`, verified in `bare-expo` that they pass.
Enable User Defined Build Settings in Release Channel (#2093)Xcode's User Defined Build Settings can (unfortunately) only be used in Info.plist so this allows you to set Expo's Release Channel ther
Enable User Defined Build Settings in Release Channel (#2093)Xcode's User Defined Build Settings can (unfortunately) only be used in Info.plist so this allows you to set Expo's Release Channel there. When you're detached, this is helpful in order to automate different Release Channels for dev, staging, prod. Additionally, when you're detached, the Version and Build of the binary should generally be part of release channel as well. Version and Build can be stored in User Defined Build Settings and used to set both CFBundleShortVersionString, CFBundleVersion and as part of ExpoReleaseChannel to avoid duplication.
[home][ios] restore QR code functionality to unrestricted IOS client builds (#3870)* [home] add QR code functionality back to unrestricted ios builds * [ios] add methods to determine client buil
[home][ios] restore QR code functionality to unrestricted IOS client builds (#3870)* [home] add QR code functionality back to unrestricted ios builds * [ios] add methods to determine client build type * pr feedback (brent) * pr feedback (eric) * add client release type header to HTTP requests for www permissions checking * [ios] use the existing provisioningprofile parser instead * [ios] fix build type logic to use new parser method
[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.
[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)
[ios] Allow apps without versioned code run if versions match (#2318)
support unsigned multimanifests (#2959)* [ios] support unsigned multimanifests* [ios] pr feedbackfbshipit-source-id: a030ae8
set isDebugXCodeScheme in EXEnvironment (#2711)fbshipit-source-id: 697040c
Clean up EXEnvironment, remove deprecated shell development config behaviorfbshipit-source-id: f4d4d01
123