[exmanifests][ios] Convert to swift (#21298)
[expo-manifests] Rename RawManifest -> Manifest (#14194)
[expo-updates] Factor out raw manifests into their own package (#14183)
[ios] Migrate all remaining native code
[ios] Migrate some packages to use expo-modules-core
[ios] Pass manifest into EXScopedFacebook (#13531)
[ios] Use stable manifest ID where applicable (#13280)
[expo-ads-facebook][expo-facebook][expo-ads-admob] Add tracking permissions (#12123)# Why Closes ENG-390 # How - Created a app tracking permission requester. - Added `requestPermissionsAs
[expo-ads-facebook][expo-facebook][expo-ads-admob] Add tracking permissions (#12123)# Why Closes ENG-390 # How - Created a app tracking permission requester. - Added `requestPermissionsAsync` and `getPermissionsAsync` methods to `expo-ads-facebook`, `expo-facebook` and `expo-ads-admob`. - Added those functions to NCL. > on Android tracking permission is always granted. # Test Plan - NCL ✅ - permissions scoping ✅ # Changelog - Added the app tracking permission.
show more ...
[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.
[expo-facebook] Native Logout and getAccessTokenAsync (#7101)* Move native code from #6862 * Update CHANGELOG.md * Update ScopedFacebookModule.java * Update EXScopedFacebook.m * Update
[expo-facebook] Native Logout and getAccessTokenAsync (#7101)* Move native code from #6862 * Update CHANGELOG.md * Update ScopedFacebookModule.java * Update EXScopedFacebook.m * Update ScopedFacebookModule.java * Update ScopedFacebookModule.java * Update Facebook.js * Update CHANGELOG.md * Updated error codes * loginMgr -> loginManager * Update facebook.md * Update facebook.md * updated comments * updated comments * Updated type names * updated types * Update facebook.md * userID -> userId * appID -> appId * Convert times to dates * updated comment * applied PR feedback * getAccessTokenAsync -> getUserAuthAsync * Update facebook.md * Update Facebook.js * Update facebook.md * Update EXScopedFacebook.m * Extract error codes to constants * FacebookAuth -> FacebookAuthentication * Update FacebookModule.java * Update CHANGELOG.md * Update ScopedFacebookModule.java * Updated doc blocks * getUserAuthAsync -> getCredentialStateAsync * getCredentialStateAsync -> getAuthenticationCredentialAsync * Update Facebook.js
[ios][facebook] add schemes for facebook login & always handle openURL in EXFacebookAppDelegate (#7931)* [ios][facebook] allow Facebook login in Expo Client app * update docs * changelog entr
[ios][facebook] add schemes for facebook login & always handle openURL in EXFacebookAppDelegate (#7931)* [ios][facebook] allow Facebook login in Expo Client app * update docs * changelog entry * fix docs: no need to go to FB app settings * Log when overriding appId in client * check for facebookAppId in case in custom client * remove method swizzling * make expokit lowest priority subcontractor * make 'priority' a method, returning NSInteger * pr feedback: conditional logging & docs * backport changes to versioned SDK 37 * revert changes to LSApplicationQueriesSchemes in info.plist * update changelog, add breaking change * update display name in info.plist
[expo-facebook] Disable autoinit (#5924)# Why Fixes https://github.com/expo/expo/issues/5702. # How According to https://github.com/expo/expo/issues/5702#issuecomment-540013928 and https:/
[expo-facebook] Disable autoinit (#5924)# Why Fixes https://github.com/expo/expo/issues/5702. # How According to https://github.com/expo/expo/issues/5702#issuecomment-540013928 and https://github.com/expo/expo/issues/5702#issuecomment-540379234. Universe PR: https://github.com/expo/universe/pull/3716 XDL PR: https://github.com/expo/expo-cli/pull/1118 # Test Plan Verified manually that: - a new experience opened up doesn't autoinitialize Facebook SDK (no request is issued, Facebook SDK remains uninitialized) - initializing manually enables login - setting `facebookAppId` in `app.json`, `autoinit: true` in JS and restarting the experience autoinitializes the SDK