Expo
42 verified issues
Typed routes not working in Expo 51 and Expo router
Minimal reproducible example https://github.com/alfjesus/typed-routes What platform(s) does this occur on? _No response_ Did you reproduce this issue in a development build? No (tested in Expo Go) Summary Creating a new project with `yarn create expo-app` (Expo 51) seems to have broken the typed routes for expo router. When I downgraded to Expo 50 (and `npx expo install --check`), typed routes started to working again. I guess there's something wrong with the generation of the types when the development server starts 🤔 Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.4.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.0 - /usr/local/bin/node Yarn: 1.22.21 - /opt/homebrew/bin/yarn npm: 10.2.3 - /usr/local/bin/npm Watchman: 2024.01.22.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.13.0 - /Users/anders/.rbenv/shims/pod SDKs: iOS SDK: Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4 IDEs: Android Studio: 2023.2 AI-232.10300.40.2321.11567975 Xcode: 15.3/15E204a - /usr/bin/xcodebuild npmPackages: expo: ~51.0.0 => 51.0.0 expo-router: ~3.5.10 => 3.5.10 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.74.1 => 0.74.1 react-native-web: ~0.19.10 => 0.19.11 npmGlobalPackages: eas-cli: 7.8.2 Expo Workflow: managed Expo Doctor Diagnostics ✔ Check Expo
May 2024 iOS privacy manifest requirements tracking issue
UPDATE We now have guide on how to add a privacy manifest via your app config (app.json / app.config.js). --- Overview Recently, Apple announced that, starting May 1, they would start enforcing that all new apps and updates must declare approved reasons for using specific APIs in a privacy manifest, preventing uploads to TestFlight if the requirement is not met. These requirements also apply to 3rd party SDK's, with specific SDK's identified by Apple requiring a signature in addition to the manifest. If you submitted to TestFlight after March 13th, you may have received an email from Apple with an "ITMS-91053" warning, indicating that they found API usage matching an `NSPrivacyAccessedAPI` category in your app that will require these changes in order to meet the requirements after May 1st (common categories might include `NSPrivacyAccessedAPICategoryDiskSpace` and `NSPrivacyAccessedAPICategoryFileTimestamp`). What Expo is doing about it Expo engineers are actively engaged with this issue, doing everything in our power ensure that your app submissions continue uninterrupted despite the relatively short notice: - Adding privacy manifests to all affected modules maintained by Expo - Tracking progress on key dependencies not maintained by Expo (e.g., this PR to add the manifest to `react-native`) and ensuring our version validation is updated accordingly as these updates go live. - Providing guidance on how to add the privacy manifest to community-maintained modules - Prov
[SDK 52] Splash screen image scaled very small on development builds
Minimal reproducible example https://github.com/expo/expo/tree/main/templates/expo-template-default What platform(s) does this occur on? Android, iOS Where did you reproduce the issue? in a development build Summary Splash screen image is scaled very small on iOS development builds, but not Expo Go. Using default template via `npx create-expo-app@latest --template default@beta` and run dev build via: `npx expo prebuild --clean --platform ios && npx expo run:ios` Screenshots to compare: Development build: Expo Go: Environment [code block] Expo Doctor Diagnostics [code block]
Xcode 16.3 and SDK 52 / React Native 0.76
Update April 3, 2025 from @brentvatne This issue is resolved. See: https://github.com/expo/expo/issues/35807#issuecomment-2776278963 <hr /> Summary After updating Xcode, running a React Native with expo app results in a build error. First, there’s a warning about a Hermes script that runs during every build because it doesn’t specify output dependencies. Then, while compiling some files, an error occurs in string_view:300:42, related to the instantiation of an undefined template (std::char_traits<unsigned char>). This seems to be caused by an incompatibility between the Xcode version, the iOS SDK, and React Native libraries. [code block] What platform(s) does this occur on? iOS SDK Version 52.0.18 Environment [code block] Minimal reproducible example npx expo install expo-dev-client npx expo prebuild npx expo run:ios
[expo-screen-orientation] Screen orientation does not lock or trigger with EAS Build
Summary On a built app with EAS build, calling https://docs.expo.dev/versions/latest/sdk/screen-orientation/#screenorientationlockasyncorientationlock does not trigger the screen to rotate and lock on iOS. When the app isn't built with EAS build, and created with expo build, the screen orientation lock async function works. Could possibly be related to: https://github.com/expo/expo/issues/11558 Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? iOS SDK Version (managed workflow only) 43 Environment Expo CLI 4.12.10 environment info: System: OS: macOS 11.6 Shell: 5.8 - /bin/zsh Binaries: Node: 14.15.1 - ~/.nvm/versions/node/v14.15.1/bin/node Yarn: 3.0.2 - ~/.nvm/versions/node/v14.15.1/bin/yarn npm: 6.14.8 - ~/.nvm/versions/node/v14.15.1/bin/npm Watchman: 2021.06.07.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.2 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 30, 31 Build Tools: 29.0.2, 30.0.2, 31.0.0 System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Android TV Intel x86 Atom, android-31 | ARM 64 v8a, android-31 | Intel x86 Atom_64, android-31 | Google TV Intel x86 Atom, android-31 | Google APIs ARM 64 v8a, androi
expo-notifications FCM V1 Migration Tracking Issue
This is a tracking issue for user-reported issues related to the Spring 2024 migration of Expo Push Notifications from FCM Legacy to FCM V1 for Android devices. There have been reported instances of brokenness in production when moving from FCM Legacy to FCM V1, and this issue will serve as a central place to track our investigation and resolution of these issues. Recommend that users should now be on `expo@51.0.24` and `expo-notifications@0.28.15` or later. The remaining issues (as of 2024-08-06) are as follows: - Issues with channel ID and vibration pattern not being set correctly in notifications - Status: In progress - ENG-12759 and ENG-12770 - Vibration pattern issue being fixed in https://github.com/expo/expo/pull/30495 - Channel issue is being worked in #30762 - Issue with custom sound not working when app in background - Status: Investigating - https://github.com/expo/expo/issues/27978 and ENG-12780 - Issue with complex remapping of notification payload on Android FCMv1 - Status: Investigating - https://github.com/expo/expo/issues/30533 Fixed issues: - null `data` payload in client when receiving push notifications - See https://github.com/expo/expo/pull/28938 - handlers are not being called when app is backgrounded - See these comments from @douglowder - handlers are being called when app is foregrounded, but app resets itself (seen in development build, unconfirmed in production) - Notification icon not working - See https://github.com/expo
[expo-notifications] notification.request.content.data is null in push notifications setup
Minimal reproducible example https://github.com/brandon-kyle-bailey/expo-notifications-bug What platform(s) does this occur on? Android, iOS, Web Did you reproduce this issue in a development build? Yes Summary Following documentation to set up push notifications and utilizing https://expo.dev/notifications to send push notifications with a data object in the message, the data object is null. Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.2.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node Yarn: 1.22.19 - ~/.nvm/versions/node/v18.13.0/bin/yarn npm: 9.2.0 - ~/.nvm/versions/node/v18.13.0/bin/npm IDEs: Xcode: /undefined - /usr/bin/xcodebuild npmPackages: expo: ~50.0.11 => 50.0.11 react: 18.2.0 => 18.2.0 react-native: 0.73.4 => 0.73.4 npmGlobalPackages: eas-cli: 7.1.2 Expo Workflow: managed Expo Doctor Diagnostics ✔ Check Expo config for common issues ✔ Check package.json for common issues ✔ Check native tooling versions ✔ Check dependencies for packages that should not be installed directly ✔ Check for common project setup issues ✔ Check npm/ yarn versions ✔ Check for issues with metro config ✔ Check Expo config (app.json/ app.config.js) schema ✔ Check for legacy global CLI installed locally ✔ Check that packages match versions required by installed Expo SDK ✔ Check that native modules do not use incompatible support p
Expo-Facebook login won't redirect back to Expo Client app when using login with Facebook app
🐛 Bug Report Environment Expo CLI 3.9.0 environment info: System: OS: macOS 10.14.5 Shell: 3.2.57 - /bin/bash Binaries: Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node Yarn: 1.19.2 - ~/.yarn/bin/yarn npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm IDEs: Xcode: 11.0/11M337n - /usr/bin/xcodebuild npmPackages: expo: ^35.0.0 => 35.0.1 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.9.0 Expo Client on iOS device Steps to Reproduce I recently tried to add login with Facebook to my application. I just copied the logIn function from here `https://docs.expo.io/versions/v35.0.0/sdk/facebook/` When I run my app via Expo Client, and execute the logIn function it 1) Redirects me to a page asking if I want to use the Facebook app for login or use phone or email 2) If I use phone or email login works perfectly fine 3) If I select `Use Facebook App` it takes me to the Facebook app, it says `You have previously logged into [MY_APP] and then I press `Continue` a white screen shows up with the `Cancel` button on the top left. It never goes back to my app and never resolves this function `logInWithReadPermissionsAsync`. Expected Behavior It should have gone back to the Expo Client app where my app was running and it should have resolved the promise and return
KeyboardAvoidingView does not work on standalone app [Android].
Hello. I have taken this code from a premium theme that i bought. [code block] Its a chat View, it works perfect on Expo testing, but as soon as I build APK standalone it does not work, the keyboard will cover the whole screen. I have tried react-native-keyboard-aware-scroll-view but in order to use its needed to detach the app. I have searched the whole internet. I'm the only one suffering from this issue?
[expo-image-picker] launchCameraAsync doesn’t open the camera on Android after the 2025-09-05 security update
Minimal reproducible example https://github.com/deka0106/expo-image-picker-test Steps to reproduce After applying the Android security patch 2025-09-05, calling `launchCameraAsync()` from `expo-image-picker` does not show the camera UI immediately. The camera only appears after the app is backgrounded and then resumed. It can be reproduced with the following steps: - Clone reproducible example - Run `pnpm install` - Run `pnpm run android` - Tap "Open Camera" When tapping "Open Camera", logcat outputs the following: [code block] I’ve confirmed the issue reproduces in the following environments: - Device: Pixel 9a, Pixel 8, Pixel 7a, Pixel 6 - Android OS: 16 - Security Update: 2025-09-05 Environment [code block] Expo Doctor Diagnostics [code block]
Specific font family setting breaks Expo go [SDK 51]
Minimal reproducible example https://github.com/SenadAlagic/expo-bug-repro What platform(s) does this occur on? iOS Did you reproduce this issue in a development build? Yes Summary As many people who transitioned to SDK 51 it didn't go smooth on my project but issues are to be expected. I ran into the issue of the app crashing and looked around and found this issue: https://github.com/expo/expo/issues/28618 which I thought was everything I needed, it described my issue perfectly and I thought that would be the end. I followed everything that was said here and still when I boot up my app on an iOS simulator it crashed immediately, BUT when I run it on my physical Android phone it works fine. I decided to strip it down and see what exactly is the cause of the issue. For some reason the issue seems to be in specifying the font-family of a Text component (default react-native's). Now, in the interest of shortening the repro I didn't assign the values "properly", the IDE does complain but the app does build and it crashes.(just pointing out that I don't have these issues and errors in my app, this is not how I change font family of text) I attributed those crashes to the new SDK version and the issue from the before mentioned GitHub issue link but this doesn't appear to be the issue with Reanimated (?). Anyways, I hope this repro is of use to you guys and I hope we can figure what exactly is the issue here. Thank you so much for your time! Steps to reproduce 1. clone
Expo start tunnel failed to start tunnel
> Jump to _official_ temporary workaround Summary Expected When running `expo start -c --tunnel` it should start up a tunnel Actual I get this error message: [code block] What platform(s) does this occur on? Android, iOS, Web Environment [code block] Minimal reproducible example Simply run the following in a terminal: [code block]
[iOS][Facebook] Not redirecting back to app after Facebook.logInWithReadPermissionsAsync through facebook app
🐛 Bug Report Environment [code block] iOS Standalone AND iOS Expo Client Steps to Reproduce Must be logged out of Facebook in the browser, but logged in in the Facebook app Facebook.logInWithReadPermissionsAsync, doesn’t come back to our app after flying to Facebook app. This may or may not occur. For now it only occurs on iOS standalone. It’s pretty strange because it’s quite strange behavior and it hurts user acquisition opportunities. This is fatal for our app. Expected Behavior After logging in with Facebook, you are redirected to our app and the login process is executed Actual Behavior Even after logging in on the Facebook app, it behaves like staying in the Facebook app. The only way to get back to our app is to cancel, and of course the login process will fail. Sample code [code block]
expo-notifications failing to get token
Summary I am having issues with expo-notifications. So I created a blank project with the expo init command, created a managed workflow, and installed expo notifications via expo install. Then I copied the `registerForPushNotificationsAsync` from here, used it in a `useEffect` hook and got the following error: `[Unhandled promise rejection: Error: Fetching the token failed: java.util.concurrent.ExecutionException: java.io.IOException: AUTHENTICATION_FAILED]` Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? Android SDK Version (managed workflow only) 45 Environment expo-env-info 1.0.5 environment info: System: OS: Windows 10 10.0.22000 Binaries: Node: 16.16.0 - C:\Program Files\nodejs\node.EXE npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD npmPackages: expo: ~45.0.0 => 45.0.6 react: 17.0.2 => 17.0.2 react-dom: 17.0.2 => 17.0.2 react-native: 0.68.2 => 0.68.2 react-native-web: 0.17.7 => 0.17.7 Expo Workflow: managed Reproducible demo https://docs.expo.dev/versions/latest/sdk/notifications/#api
Execution failed for task ':expo-modules-core:compileReleaseKotlin'.
Summary FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':expo-modules-core:compileReleaseKotlin'. > A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction > Compilation error. See log for more details Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. BUILD FAILED in 3m 26s Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.10.2/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. 549 actionable tasks: 549 executed Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information. Managed or bare workflow? managed What platform(s) does this occur on? Android Package versions [code block] Environment [code block] Reproducible demo Hi i have found this error when i do eas build through expo.dev Stacktrace (if a crash is involved) _No response_
Expo ImagePicker fails to launch. Call to function 'ExponentImagePicker.launchCameraAsync' has been rejected.
Summary My users on Android arrive at a point where they can no longer launch the camera. User has given camera and media library permissions. User was able to open camera. User is no longer able to open Camera or Media Library. It seems to be related to the expo task manager too. I've found that the issue appears when: - Given you are tracking location via a task in the task manager - When you close the app - When you reopen the app - When you try to pick an image - Then the image picker will not open I've found that the issue does not appear when location tracking is not active when the app was last closed. Check the linked repo with reproducible example. [code block] Resulting error logs (source Sentry): [code block] Closing and reopening the app does not resolve the issue. Once a user has met this error, only reinstalling the app works. What platform(s) does this occur on? Android Environment expo-env-info 1.0.5 environment info: System: OS: macOS 12.0.1 Shell: 3.2.57 - /bin/bash Binaries: Node: 16.12.0 - ~/.nvm/versions/node/v16.12.0/bin/node Yarn: 1.22.17 - /usr/local/bin/yarn npm: 8.1.0 - ~/.nvm/versions/node/v16.12.0/bin/npm Watchman: 2021.06.07.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5 IDEs: Android Studio: 4.1 AI-201.8743.12.41.7199119 Xcode
expo-splash-screen preventAutoHideAsync() seems to have no effect
TEMPORARY SOLUTION: The bug is in 0.27.6 - downgrade to 0.27.5 Minimal reproducible example https://github.com/jaworskimatt/splashscreentest What platform(s) does this occur on? iOS Where did you reproduce the issue? in Expo Go Summary Calling `SplashScreen.preventAutoHideAsync();` seems to have no effect on the app, the splash screen is automatically hidden. Steps to replicate: `npx create-expo-app@latest splashcreentest` to deploy a fresh app Edit `app/_layout.tsx` and comment out or delete `SplashScreen.hideAsync();` `npx expo start` Expected result: Since hideAsync() is not called, the splash screen should stay forever Actual result: The splash screen auto-hides anyway Environment [code block] Expo Doctor Diagnostics [code block]
useFonts hook randomly failing to load fonts
Summary When I use the {useFonts, Abel_400Regular} hook from "@expo-google-fonts/abel" and {HankenGrotesk_300} from "@expo-google-fonts/hanken-grotesk" the Abe font will fail to load on my iOS Expo Go app and my Android studio emulator. However, when I add the function [code block] and save my editor the font loads fine. But when I reload each app from Expo Cli the font refuses to load again unless I remove the function, save in my editor, add the function, and save again. I had this issue earlier with locally saved .otf font files, so I believe the issue is with the { useFonts } hook. I've tried all fixes I can find online and nothing's helped. EDIT: I found out it's loading the fonts whenever I hot-reload after changing any code in the render return statement for a function component. I just added an if (fontsLoaded) {} and saved and it loaded the fonts. I'm guessing it's throwing the Font not loaded error slightly before the font gets a chance to load, but when I use a splashscreen to wait for it to load it gets stuck on the splashscreen forever. What platform(s) does this occur on? Android, iOS SDK Version ~48.0.9 Environment [code block] Minimal reproducible example Here is the minimum code I was able to reproduce the error with. When I change the return statement and hot-save the project, the render update fixes the font. [code block] Here is one of the screens the font is running on ```
Location: "Location provider is unavailable. Make sure that location services are enabled."
🐛 Bug Report Environment Expo CLI 2.19.5 environment info: System: OS: macOS High Sierra 10.13.6 Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.1 - /usr/local/bin/node Yarn: 1.13.0 - /usr/local/bin/yarn npm: 6.4.1 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.1 AI-173.4670197 Xcode: 10.1/10B61 - /usr/bin/xcodebuild npmPackages: expo: ^34.0.1 => 34.0.3 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-34.0.0.tar.gz => 0.59.8 react-navigation: ^3.11.1 => 3.11.1 APP TARGET : ANDROID DEVICE (USING EXPO CLIENT APP). Using a VIVO Device running Android 6.0, the device has a SIM and is network enabled. Steps to Reproduce let { status } = await Permissions.askAsync(Permissions.LOCATION); if (status !== 'granted') { this.setState({ errorMessage: 'Permission to access location was denied', }); console.log("no permission"); } else{ console.log("working on location"); let location = await Location.getCurrentPositionAsync({enableHighAccuracy:false}); console.log('latitude is ' + location.coords.latitude.toString()) console.log('longitude is ' + location.coords.longitude.toString()) } Expected Behavior The location services should provide me with GPS coordinates. Actual Behav
Not valid sdk version after upgrading Android Expo app (
I have Android Expo app (v. 2.10.0) downloaded from the Play Store. I try to run a new Expo project: [code block] Then I open the app on my device and get a blue screen with: "Something went wrong. 31.0.0. is not a valid SDK version. Options are 32.0.0, UNVERSIONED." How can I use Expo app on my device with expo project which uses < 32.0.0 expo version?
NotificationResponseReceivedListener not called when app is killed
Summary I ran into problems while developing an app that has to respond to push notifications. I based this app on the expo notification snack that is found in the documentation. When trying out my app, the expo notification service works fine when an app is in the foreground or background, but does not trigger when the app is killed. I use the addnotificationresponsereceivedlistenerlistener method to handle notifications when the app is killed. I found a lot of issues about this problem that have already been closed. Unfortunately, the solutions/pull request in these issues don't solve the problem on my system. I therefore think this might be a bug that was introduced in version 42 of the expo SDK. Related issues - https://forums.expo.dev/t/push-notification-doesnt-open-specific-screen-when-app-is-killed-works-only-in-foreground-and-background/53890/5 - https://github.com/expo/expo/issues/13333 - https://github.com/expo/expo/issues/12954 - https://github.com/expo/expo/issues/12228 - https://github.com/expo/expo/issues/11933 - https://github.com/expo/expo/issues/11470 - https://github.com/expo/expo/issues/11340 - https://github.com/expo/expo/issues/10621 - https://github.com/expo/expo/issues/9968 - https://github.com/expo/expo/issues/6943 Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? Android SDK Version (managed workflow only) 42.0.1 Environment [code bloc
Expo Facebook returns cancel with native IOS facebook app on successful login
🐛 Bug Report Environment Expo CLI 2.20.2 environment info: System: OS: macOS 10.14.5 Shell: 5.3 - /bin/zsh Binaries: Node: 12.1.0 - /usr/local/bin/node npm: 6.9.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild npmPackages: expo: ^33.0.0 => 33.0.7 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz => 0.59.8 react-navigation: ^3.11.0 => 3.11.0 npmGlobalPackages: expo-cli: 2.20.2 iOS standalone app Steps to Reproduce 1. Use Facebook.logInWithReadPermissionsAsync to make a facebook login. 2. Choose to log in with the Facebook native app(not in the browser) 3. Press continue to get back to your app. Expected Behavior 3. User should be successfully logged in after getting redirected back to the app Actual Behavior 3. The promise returns type === cancel no matter what the user actually does. *Note: This seems to only happen to some users, but most of the time it does not work. I'd say 1/10 people actually manage to log in the first try. Reproducible Demo In the view I have: <TouchableOpacity onPress={this._handlePressAsync}> <Image source={facebookLogin} style={styles.facebookLogin}/> </TouchableOpacity> The function called: _handlePressAsync = async () => { const {type, token,} = await Facebook.logInWithReadPermission
Expo build failed / SDK 48
Summary Build failed after update to SDK 48 (from SDK 46). No any errors while application running in development mode. Any help? What platform(s) does this occur on? Android SDK Version 48 Environment System: OS: macOS 13.2.1 Shell: 5.8.1 - /bin/zsh Binaries: Node: 16.16.0 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 8.11.0 - /usr/local/bin/npm IDEs: Xcode: /undefined - /usr/bin/xcodebuild npmPackages: @expo/metro-config: ^0.5.2 => 0.5.2 @expo/webpack-config: ^18.0.1 => 18.0.1 expo: ^48.0.0 => 48.0.8 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.71.3 => 0.71.3 react-native-web: ~0.18.11 => 0.18.12 Expo Workflow: managed Minimal reproducible example package.json [code block] Stacktrace (if a crash is involved) [code block]
Auth session sometimes ends with "Something went wrong trying to finish signing in."
Maintainer edit The auth session proxy service is deprecated and not recommended for production. For production apps, your app should navigate to the third-party authentication provider directly instead of using this service. This is the official workaround to this issue, which is likely unresolvable due to how browser cookie policies have changed. Follow this migration guide if you are currently using the proxy service. The migration guide shows how to configure the authentication provider to redirect directly to your app, typically with a deep link with your app's own URL scheme. In your app, set the useProxy option to false (the default) when calling the promptAsync method, which configures your app not to use this service. Due to web browser changes like WebKit's Tracking Prevention, the AuthSession proxy service may not work reliably in edge cases such as when a user's device is configured to block cookies or prevent cross-site tracking. The AuthSession proxy service does not track nor collect any user data but it requires cookies to correctly redirect back to your app after the user has authenticated with the third-party authentication provider. This service will not work if the browser's settings or heuristics block cookies. --- 🐛 Bug Report Summary of Issue (just a few sentences) Sometimes when I try logging in using AuthSession it doesn't redirect me back to app, but shows "Something went wrong trying to finish signing in." instead. After that when I try agai
'Could not encrypt/decrypt the value for SecureStore' error on android app
Minimal reproducible example https://snack.expo.dev/@simranjits11/error-with-securestorage Summary Context When trying to get item using `await SecureStore.getItemAsync('mobile')`. It throws an error saying `Could not encrypt/decrypt the value for SecureStore`. The error is very device specific and happens occasionally. - Message: Error: Could not encrypt/decrypt the value for SecureStore . - SDK: 47.0.12 - Device: OnePlus 8T (Android 13) Stack Trace [code block] Environment expo-env-info 1.0.5 environment info: System: OS: macOS 13.3.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 9.6.7 - ~/Documents/Projects/realmagic/node_modules/.bin/npm Watchman: 2023.02.20.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.3 - /Users/simranjitsingh/.rbenv/shims/pod SDKs: iOS SDK: Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4 IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7678000 Xcode: 14.3/14E222b - /usr/bin/xcodebuild npmPackages: react: 18.1.0 => 18.1.0 react-dom: 18.1.0 => 18.1.0 npmGlobalPackages: eas-cli: 3.15.0 expo-cli: 6.3.2 Expo Workflow: managed
Recent increase in 'No matching activity' errors from `WebBrowser.openBrowserAsync()`
Summary An app in production since August 2020 that launches a web browser using `WebBrowser.openBrowserAsync()` is failing to do so without throwing 'No matching activity' errors on some Android devices, but with an increasing frequency during 2021 so far. It seems to be mostly affecting devices running Android 11 (a full list of device models is available). Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! bare What platform(s) does this occur on? Android SDK Version (managed workflow only) _No response_ Environment Expo CLI 3.28.5 environment info: System: OS: macOS 10.15.7 Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.19.0 - /usr/local/bin/node npm: 6.14.11 - /usr/local/bin/npm Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 IDEs: Xcode: 12.4/12D4e - /usr/bin/xcodebuild npmPackages: expo: ^37.0.0 => 37.0.12 react: 16.9.0 => 16.9.0 react-dom: 16.9.0 => 16.9.0 react-native: 0.61.4 => 0.61.4 react-native-web: ^0.11.7 => 0.11.7 react-navigation: ^4.0.10 => 4.4.0 npmGlobalPackages: expo-cli: 3.28.5 Expo Workflow: bare Reproducible demo or steps to reproduce from a blank project [code block] The issue above is occurring with increasing frequency on an app in production on Expo 37. I am aware of `We
Plugin [id: 'com.facebook.react.settings'] was not found in any of the following sources
Summary Starting today, running `expo run:android` my build would very quickly fail with [code block] The relevant line (settings.gradle line 4: `plugins { id("com.facebook.react.settings") }`) was recently added to the `expo-template-bare-minimum` package, which the CLI pulls remotely and therefore cannot be versioned by our app. The new plugin (`com.facebook.react.settings`) was apparently introduced in react-native 0.75.0, and then stubbed in 0.74.4 in order to allow Expo to support both 0.74 and 0.75 with Expo 51 (https://github.com/facebook/react-native/pull/45720) I have fixed the problem by updating from react-native 0.74.3 to 0.74.5 (the current recommended version for Expo 51). What platform(s) does this occur on? Android SDK Version 51 Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.5 Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.1 - /opt/homebrew/opt/node@18/bin/node npm: 10.2.4 - /opt/homebrew/opt/node@18/bin/npm Managers: CocoaPods: 1.15.2 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5 Android SDK: API Levels: 31, 33, 33, 34 Build Tools: 30.0.3, 33.0.0, 33.0.1, 33.0.2, 34.0.0 System Images: android-32 | Google APIs ARM 64 v8a, android-34 | Google Play ARM 64 v8a IDEs: Android Studio: 2024.1 AI-241.18034.62.2411.12071903 Xcode: 15.4/15F31d - /usr/bin
Android standalone app crashing on Android X
Hi expo team, I did update SDK yesterday. (35 to 36). Android build does not work on android x versions. The application gives error after splash screen. "Application keep stopping". and no error. I'm just getting unsafe lifecycle methods warning from GridList and Hyperlink packages. I uninstalled and tried these packages, but the problem persists. But there is a detail; The application opens smoothly on first installation. But if you close it through the task manager it won't open again. Expo CLI 3.11.1 environment info: System: OS: macOS 10.15.1 Shell: 5.7.1 - /bin/zsh Binaries: Node: 10.17.0 - /usr/local/opt/node@10/bin/node Yarn: 1.19.1 - /usr/local/bin/yarn npm: 6.11.3 - /usr/local/opt/node@10/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.5 AI-191.8026.42.35.5900203 Xcode: 11.1/11A1027 - /usr/bin/xcodebuild npmPackages: expo: ^36.0.0 => 36.0.0 react: 16.9.0 => 16.9.0 react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.11.1
[expo-updates] [SDK 49] Presence of expo-updates causes production build to crash on launch
Minimal reproducible example https://github.com/mikescott/expo-updates-crash Summary The presence of expo-updates causes production and simulator builds to crash on launch. I discovered this after upgrading a project to SDK 49. The issue does not happen in SDK 48. To reproduce 1. Build the app: `eas build --platform=ios --profile=simulator` 2. Run the app in an iOS Simulator The app will crash with the following report: [code block] To fix the app: 1. `yarn remove expo-updates` 2. `eas build --platform=ios --profile=simulator` 3. App will launch successfully Environment [code block]
Expo EAS build fails: runtimeVersion policy not supported in bare workflow
Expo EAS build fails for projects in the bare workflow when app.json uses `"runtimeVersion": { "policy": "appVersion" }`. The policy-based runtime version is only supported in managed workflow projects. Bare workflow projects must set runtimeVersion to a literal string matching the version field. AI-generated app.json files and Expo documentation examples often show the policy form without this distinction.
Expo React native new EAS build blank white screen
Summary When i Created a APK build using EAS it just shows me white screen and there is also no logo of my app after installing meanwhile when i use in locally using Expo app the app is working perfectly fine and my app also have splash screen and logo. This is my eas.json { "cli": { "version": ">= 7.1.2" }, "build": { "development": { "developmentClient": true, "distribution": "internal" }, "preview": { "distribution": "internal" }, "production": { "android": { "buildType": "apk" } } }, "submit": { "production": {} } } What platform(s) does this occur on? Android SDK Version "expo": "^51.0.10", Environment expo-env-info 1.2.0 environment info: System: OS: Windows 10 10.0.19045 Binaries: Node: 21.6.2 - C:\Program Files\nodejs\node.EXE npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: AI-231.9392.1.2311.11330709 npmPackages: expo: ^51.0.10 => 51.0.10 react: ^18.2.0 => 18.2.0 react-native: 0.74.1 => 0.74.1 Expo Workflow: managed Minimal reproducible example NA
[expo-constants][iOS] build failed: PhaseScriptExecution [CP-User]\ Generate\ app.config\ for\ prebuilt\ Constants.manifest
Summary expo-constants throws 'Command PhaseScriptExecution failed with a nonzero exit code' when building iOS. Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! bare What platform(s) does this occur on? iOS SDK Version (managed workflow only) _No response_ Environment [code block] Reproducible demo This doesn't require any code to reproduce. Just create a new project and build its iOS on XCode. - Step 1 [code block] - Step 2 [code block] - Step 3 [code block] - Step 4 In XCode, select a team for signing - Step 5 Build and wait. - Step 5 Say hi to the error: [code block]
'SplashScreen.show' has already been called for given view controller.
Summary This warning comes up on initial launch. Also I somtimes still get the ' No native splash screen registered for given view controller. Call 'SplashScreen.show' for given view controller first' error even though i'm upgraded to the latest beta which was supposed to address this issue Managed or bare workflow? If you have made manual changes inside of the `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? iOS Environment Expo CLI 4.12.6 environment info: System: OS: macOS 11.6 Shell: 5.8 - /bin/zsh Binaries: Node: 14.15.1 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.8.0 - /usr/local/bin/npm Watchman: 2021.10.04.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0 IDEs: Android Studio: 4.1 AI-201.8743.12.41.6858069 Xcode: 13.0/13A233 - /usr/bin/xcodebuild npmPackages: expo: ^43.0.0-beta.4 => 43.0.0-beta.4 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.2 => 0.64.2 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: expo-cli: 4.12.6 Expo Workflow: managed Reproducible demo or steps to reproduce from a blank project https://github.com/haibert/SplashScreenIssue I created a blank project with a custom dev c
Error resolving plugin [id: 'com.facebook.react.settings']
Minimal reproducible example https://github.com/BraveEvidence/SampleExpo What platform(s) does this occur on? Android Where did you reproduce the issue? in a development build Summary I created a simple Expo Project using `npx create-expo-app@latest --template blank-typescript`, I need to write native android code so I did following `npx expo install expo-dev-client` `npx expo run:android` `npx create-expo-module@latest --local` I have the necessary Android Setup on my Mac like Android Studio, Java etc When I open the android folder in Android Studio I get following error during gradle sync. I have not written a single line of code [code block] Environment [code block] Expo Doctor Diagnostics [code block]
[docs] No native ExpoFirebaseCore module found with firebase-recaptcha
[https://docs.expo.io/versions/latest/sdk/firebase-recaptcha/] I followed the steps described in this doc to set up the phone auth but ran into the issue of "ExpoFirebaseCore module not found, are you sure the expo-firebase-core module is linked properly?" I installed the expo-firebase-core package too but still ran into this error. How to fix it?
[android][expo-image-picker] content:// URIs are not usable in `ExponentImagePicker.launchImageLibraryAsync`
Minimal reproducible example I don't have Android. I have no idea what is an `uri` with `content://` Summary "expo-image-picker": "~14.3.2", Exactly as it's happening here https://github.com/expo/expo/issues/9354, I'm getting an error in `ExponentImagePicker.launchImageLibraryAsync` [code block] For some reason, after upgrading to Expo 49, seems like the image picker totally changed (the UI) in Android, and it seems like it allows the user to pick photos that the URI are `content://xxxx` As you can see here, it's only happening since some days ago (when I published SDK 49 upgrade). <img width="323" alt="Screen Shot 2023-08-29 at 21 59 44" src="https://github.com/expo/expo/assets/1837969/9aef3e41-0f95-4725-b2a6-adea4533eb63"> Is there a workaround for this? Maybe some available flag to switch back to the old UI version, where files with `content://` uris were not visible. Current code: [code block] Environment [code block] "expo-image-picker": "~14.3.2",
React Native app shows blank screen after Expo SDK upgrade
After upgrading Expo SDK, the app shows a blank white screen with no error visible. The root cause is usually a Metro bundler cache containing stale pre-upgrade build artifacts, or a native module that requires a fresh `npx expo prebuild` to regenerate platform-specific code after the SDK version change.
Upgrading to expo@44.0.0 breaks iOS build of amazon-cognito-identity-js
Summary I use `amazon-cognito-identity-js@5.1.0` in my project as well as `expo`. I tried upgrading to `expo@44.0.0`, but the iOS build then fails with a lot of errors, e.g: [code block]` Build log is attached: expo-44-build-error.txt This build error does not occur with `expo@43.0.3` Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! bare What platform(s) does this occur on? iOS SDK Version (managed workflow only) _No response_ Environment [code block]` Reproducible demo I created a minimal reproducer here: https://github.com/schiller-manuel/expo-issue The project was created using these steps: 1. `npx react-native init ExpoIssue --template react-native-template-typescript` 2. `npm install amazon-cognito-identity-js && npx pod-install` 3. `npx install-expo-modules` Run `npm run ios` to reproduce the build errors.
Document picker not working with publish iOS app
I am using DocumentPicker API to upload files. Its working well with android application, both with expo client and published apps. But for some reason, its not working with iOS platform. Do I need to define some permission or something??? I'm using sdk v20.0.0
[unimodules][android][notifications] Event listener can miss `emit()` calls made soon after app launch
🐛 Bug Report Summary of Issue If you call `Notifications.addResponseReceivedListener` in `useEffect` for example, the listener will not be triggered when opening an app from a completely killed state via a notification. This can also be demonstrated by adding a timeout to `componentDidMount` as shown here. Without 1 second timeout- events come through; with 1 second timeout- event's do not come through. I should note that the emit method is getting called in this case. Environment - output of `expo diagnostics` & the platform(s) you're targeting Reproducible Demo https://snack.expo.io/@charliecruzan/push-notifications Steps to Reproduce Need to run the app as a published experience or standalone app (or bare debug build) to see the behavior. Press "show notification" and kill the app, tap the notification, observe that response listener isn't triggered. Workaround The workaround (and possibly long-term solution) is to add the listener outside of any component, then it works as expected (presumably bc of how much sooner it's getting called?). I changed the docs to suggest this so fewer people run into this issue
BackgroundFetch not running
Environment [code block] app's target - iOS, Standalone Steps to Reproduce 1. Allow background fetch in app.json [code block] 2. define a task in App.js [code block] 3. register task at some point of the apps running [code block] 4. set minimum interval for task in seconds `BackgroundFetch.setMinimumIntervalAsync(60);` Expected Behavior App should periodically call my server to log that the background task is running Actual Behavior Never see the background task run, although i do see the logs that show the background task was registered. The logging service i use has been used to show when location background task has run so this logging service should log if the task runs My main question is has anyone seen background fetch run? if so have i just configured it wrong?
iOS WKWebView blocks requests to localhost API in development builds
A React Native app using WKWebView (or Expo WebView) cannot make HTTP requests to a local development API (http://localhost:3000) on a physical iOS device. iOS enforces App Transport Security (ATS) which blocks all cleartext HTTP connections. Simulators work because they share the Mac's loopback interface, but physical devices cannot reach the Mac's localhost.