Expo sdk 48 github Find and fix vulnerabilities Actions. Is there any more information I can give you to help debug it? I haven't been able to find anything wrong with the config plugin other than outdated versions of the sentry SDKs in package. json file, adding the below code the build is successful but the apps In today's announcement from Expo, they released the latest release of their software development kit, SDK 48. Minimal reproducible example import { initializeApp, getApp } from "firebase/app"; import { getAuth, PhoneAuthProvider, signInWithCredential, updateCurrentUser Currently Expo Web support is not production ready, but if you want to see how this project looks on the web as a PWA (Progressive Web App) using react-native-web and react-dom. 2, create splash screen from the guide Summary i followed this guide here for iOS, but the app will crash when showing the splash screen. 1 as bumping expo Install past and current versions of Expo Go. Contribute to RoutinelyMagical/Expo-48-reference-installation development by creating an account on GitHub. In its current form, this plugin relies heavily on regex based mods in order to function, which means with every new expo SDK (which means every react-native update (which means every Podfile change)), we need to recertify that this plugin works. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Assignees No one assigned Suddenly, Expo SDK 48 iOS build failed in the fastlane #2169. 0). I checked, the onChangeIndex will be called immediately when the list is rendered. Resources "How do I ask a good question?" "Join the community" Check that native modules use compatible support package versions for installed Expo SDK. Pick a username [SDK 48 beta. 0, the apps no longer receive updates when I run the same command. After you mentioned the reproducible built for you, I tried building my project and the reproducible separately. After this happened, my local running of my app in ExpoGo broke. Create an emtpy project with expo SDK 48; copy code from sample and run VSCode extension for React Native - supports debugging and editor integration - [Feature] Update documentation for Expo SDK 48 · Issue #1918 · microsoft/vscode-react-native Hello! Our GitHub issues are reserved for bug reports. Environment. And then running run Environment expo-env-info 1. SDK 48 on Android build Failing #342. 48. 3. Contribute to pchmn/test-expo-sdk-48 development by creating an account on GitHub. 3 | Expo SDK 48; Firebase SDK version: Firebase v9. 0. I recently decided to upgrade my project from Expo SDK 48 to SDK 50. In my case I had the BRANCHS(EAS): production, development peterpme changed the title SDK ~48. 5 environment info: System: OS: macOS 12. On real android device, tap to notification is not navigating to specific screen. 9 - /bin/zsh Sign up for free to join this conversation on GitHub. Overview. 49. /sdk-48 --template blank@48. Plug in your Android phone to this computer. Not quite sure how already closed issue (#320 #292) are observed - probably not so much, so that's the reason why I'm opening up this issue. On Android it works fine. 0 in expo sdk 48 (should be ~@6. An open-source framework for making universal native apps with React. Open edilsonlsouza opened this issue Jan 6, 2024 · 15 comments Before submitting an issue on GitHub, please follow the guide above and make sure your project is set up correctly. Closed MuflahNasir opened this issue Oct 10, 2023 · 7 comments Sign up for free to subscribe to this for expo-cli publish issue, could you elaborate what's the steps you did? that would help us to investigate the problem. But, you can also upgrade to Expo SDK 48, and use Firebase 10. 2. https://devblogs. 0 or another more recent version - it just won't work in expo go, but works fine with development builds and release builds, as @flexbox pointed out. I took this sample app and updated my dependencies to match the latest Expo SDK 48 release. com/gloredo/expo-sdk-49-downloaded-file-issue/tree/main Summary After updating SDK 48 to 49, the . npx expo run:ios --configuration Release compile but app crashes when opened. Migrating to react-native-firebase, imo, has been the best decision of my week. I found this as a solution in another Github issue. 6. I just upgraded to Expo 48, but now the prebuild fails. for example, after upgrading from sdk 47 -> 48, you should create a new sdk 48 based app. However, the event disappears as soon as we upgrade to SDK 49. Ensure you have Expo Orbit installed. > Could not create an instance of type com. I tried to update expo-image-picker to the latest (14. In addition, I'm also using the url parameter because I have my own Sentry server. Automate any Summary Hey, I'm trying to install your package to work with Expo version 48. Reproducing this is as easy as it gets. gms:play-services-location dependency is potentially a breaking change to some projects (as we are finding out) which is why I assume react-native-maps expo-community / expo-server-sdk-python Public. In publishing an update to a branch in EAS, the "updates" section was added to my app. However, we can’t promise any sort of timeline for resolution. If you have a question about Expo or related tools, please post on our forums at https://forums. 5 environment info: System: OS: macOS 13. Contribute to gaishimo/expo-sdk-48-example development by creating an account on GitHub. Sign up for a free GitHub account to open an issue and contact its 🎉 It's happened! Flipper support is now a natural part of your expo build via the official build-properties plugin. Notifications You must be New issue Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the error: invalid token. 9. However, it fails to build at the step Run gradlew and Install pods on Android and iO Is there a way to support expo-sdk >= 48 with a newer react-native-web that has dropped setNativeProps ? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. 0, while gifted chat uses 4. 8 expo: 48. I originally posted the solution on StackOverflow. This package has been removed as of SDK 48. Expo SDK 48 / Android Build Failure with "Execution failed for task ':app:checkDebugAarMetadata'. I'm encountering a strange issue when trying to build an APK. Install the new Instantly share code, notes, and snippets. 1 as a peer dependency which leads to the registration of two views: Invariant Violation: Tried to register two views with the same name RNCSafeAreaProvider, js engine: hermes. Sign up for GitHub By clicking “Sign up for GitHub”, Prior to the update, I was running the command eas update --branch dev --message "Updating the app" to update my apps, and it worked fine with Expo SDK 48. I have a bit more information in case it helps those triaging, although @cmot17's info above is amazing and the reproducible example works for me too:. When I revert back to SDK 48, I can see that the event is still being called. md at main · expo/expo On expo SDK 48, react-native-safe-area-context is upgraded to version 4. It was working fine before, but after I updated Expo SDK from 46. . After these steps have been completed, the Snack website can be deployed After seeing the references to updates near the top of the report I had a hunch to remove the expo-updates package (which I don't even use), and rebuild my app. This error is saying that your SDK version should be 43 down to 40, but your Here’s how to upgrade your app to Expo SDK 48 from 47: Update to the latest version of EAS CLI (if you use it): npm i -g eas-cli. Dev with Expo Web. json. Which is very annoying. So it's clearly an issue with the last work that's meant to fix the trigger mapping, but instead it's causing crashes. 71. 1 Shell: 5. Assignees No one assigned Why. Specific utilities used: Forms, modals, navbar, expo sdk, secure store, local notifications, social sharing, animations, gestures, favorites Summary I created a new bare project and added expo-updates. microsoft. Unfortunately, I cannot run or build the app outside of my native environment using EAS whenever I update reanimated to expo's recommended version for Expo 48 (Reanimated 2. mjs extension to metro config. json, and running npx expo-doctor. variant. 18 #23125. 69. This module provides access to the Firebase configuration and performs initialisation of the native we always recommend reviewing the update helper diff in our upgrade instructions in sdk release notes. Upgrade expo to SDK 48 Find and fix vulnerabilities Actions. 1 - /bin/zsh Binaries: Sign up for free to join this conversation on GitHub. 2. json is 48. I did remove sdkVersion": "47. " #23487. After the update to Expo SDK 49. Navigation Menu Toggle navigation. Summary After upgrading to SK react native expo-sdk 48 ios build issue. 18 project: expo managed OS: windows I was trying to build an apk and share an expo pre-release build of my app by using the "eas build -p android --profile Summary. 0 Shell: 5. Saved searches Use saved searches to filter your results more quickly You signed in with another tab or window. 5 environment info: System: OS: Windows 10 10. Closed gur22-09 opened this issue Jun 27, 2023 · 2 comments Contribute to pchmn/test-expo-sdk-48 development by creating an account on GitHub. 6 to 0. Minimal reproducible example create a new module with an example project npx create-expo-module my-module Sign up for a free GitHub account to open an issue and contact Jump to bottom. Develop an app with we still use react-native-svg@13. npm install npx eas build --platform ios Summary I'm having a Expo app (SDK 48) within a mono-repo and trying to deploy it as builds for both Android and iOS by using command eas build -p all. You signed out in another tab or window. After migrating to Expo SDK 48, I found out that it is not working on Android anymore. 1 - /bin/zsh Binaries: After some more checking, it is not caused by React-Native. expo. It worked. Presumably ahead of SDK49, expo Contribute to pchmn/test-expo-sdk-48 development by creating an account on GitHub. Find and fix vulnerabilities Codespaces Contribute to gaishimo/expo-sdk-48-example development by creating an account on GitHub. And for the swiper flatlist with a given start index, it will jump to 0 immediately. Tera suporte ao expo Sdk 48? Fiz a atualização aqui e deu o seguinte problema: Expected package @expo/config-plugins@~6. Hi, I am upgrading an app from Expo 47 to Expo 48. PWA: Expo Spotify looks best on a mobile device, but not bad on desktop!. Just upgraded to SDK 48, made a new build, ran Updates. android. Curiously enough everything works on certain devices but not others (iPhoneX works, but does not on iPhone 12) with the exact same build. Sign in Product Actions. 8, after yarn install npx expo run:android —variant release doesn’t compile. json: "resolutions": { Learn about the changes, how to try it out, and how to give feedback. 1 100 lines of "react-navigation failed to find sourcemap" issue Feb 17, 2023 peterpme mentioned this issue Feb 17, 2023 Description. Skip to content Toggle navigation. 5 environment info: System: OS: macOS 14. Summary The current expo package in my package. Sign in Product You signed in with another tab or window. 17. Tip: You can create a new SDK 48 project using npx create-expo . I am having much time trying to run web in expo SDK 49 which previously worked well in 48. mjs this causes the Contribute to pchmn/test-expo-sdk-48 development by creating an account on GitHub. Ensure your Android phone is the selected device in Orbit: I just updated my project to expo SDK 48. But after I upgrade my APP to expo SDK 48, Google Play reports my app has advertisement SDK, and the SDK is AdMod Summary Updated expo and react-native packages according to beta blog post and re-ran development eas build for ios simulator, Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I You'll need to update your version of the Expo SDK using the "expo upgrade" command. Saved searches Use saved searches to filter your results more quickly Expo Router v1. com/typescript/announcing-typescript-5-0-beta. my app using expo SDK 48 a Browser version: React-native v0. 4; React Native Gesture Handler version: 2. Automate any workflow Packages. Expo runs on Android, iOS, and the web. Expo Modules unable to run android example app on SDK version 48. reloadAsync on the first app launch, didn't crash. Closed Robogram opened this issue Nov 3 Hi @brentvatne!Thanks for helping out on this one. The first image You signed in with another tab or window. 20. 3 Shell: 5. Find Summary I am running Expo SDK 48 and getting setup with EAS. See our Using Firebase guide for how to use the Firebase JS SDK or React Native Firebase directly. Reload to refresh your session. expo-env-info 1. 2 @expo/config-plugins@8. json?I think you need to either set useClassicUpdates to true (if using the classic update mechanism), or set a url for using the newish EAS Updates. launchCameraAsync #24799. This blog will delve into the various changes and improvements that accompany this update. appDelegat Minimal reproducible example https://snack. @iodriller @rc-markzhou I solved the issue upgrading to Expo SDK 48 and stop using Firebase JS SDK. googleMapsApiKey) when prebuilding there is My SDK 48 build work good! I am build and submit application to the Play Market and Google Store! Two weeks after I published programs in the Market/Store - my client asked to make minor changes in the color scheme. Sign in Product GitHub Copilot. If you still use this package, see our Migration Guide for help upgrading. x. Automate any workflow Codespaces Summary. if you have any doubt about the changes suggested in upgrade helper diffs, you can refer to a new project on Just to +1 this as I ran into this upgrading a project to SDK48 just now. Expo constants seem to be undefined in a built APK but works for iOS build, android simulator and iOS simulator. [Expo-SDK-48] App crashes when calling ImagePicker. However, since the upgrade, the progress event on the upload is no longer being called. Host and manage packages Security. But when compiling the ios Contribute to gaishimo/expo-sdk-48-example development by creating an account on GitHub. Make a blank new app, It appears that sentry-expo does not work with EAS on Android with SDK 48. build. (Yarn is recommended) None Summary Expo SDK 48 is being used in demo in the RouterV2 demo router-demo However stated Expo SDK 49 is needed in multiple places https: Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Instant dev environments React Native or Expo version: react-native: 0. json (saved the list for later); npm install Been using this in Expo 48 and Skip to content. You signed in with another tab or window. impl. The SDK 48 beta period will last approximately a week, and it is an opportunity for developers to help ensure that the new release does not Let’s get our hands on the newest features introduced in Expo SDK 48: Expo router, Expo Image, faster EAS builds with M1 React Native Mastery - Launched! Master React Native and Expo by building 7 real-world Summary Build keeps failing for SDK 48, few weeks back the build working, now the build keeps failing If in eas. Navigation Menu GitHub community articles Repositories. I narrowed it to expo-updates or expo-dev-client, but likely expo-dev-client. Since the native code in the guide here has changed Summary I recently wanted to upgrade my expo sdk from 47 to 48, after changing the expo version in package. reCAPTCHA components for Firebase phone authentication 📱 Minimal reproducible example You should be able to reproduce this just by upgrading to SDK48, having "facebookScheme", "facebookAppId" and "facebookDisplayName" in your app. This is the Sign up for a free GitHub account to open an issue and contact its We’ll occasionally send you account related emails. It makes adding new routes as easy as creating a file in your project directory. I'm not entirely sure which step fixed it. React Native version: 0. Write better code with AI Security. dev/ or join our Discord at https://chat. 8. 2 worked fine on Android and iOS with Expo SDK 47. 16. 5, yet it gives me this error: npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: testing1@1. Summary I was using expo sdk 43 before, and always use expo start to create a local host and work on my android phone. Find and fix vulnerabilities Codespaces. Topics Trending Collections This repository includes the Expo SDK, Modules API, Go app, CLI, Router, documentation, Summary [stderr] Error: [ios. Home Guides EAS Reference Learn. 5 environment info: S I'm encountering some strange behaviour also with static assets, and I'm also using expo-updates. Steps to Reproduce. While I can successfully build the app for iOS, I am encountering Kotlin compile errors during th Minimal reproducible example https://github. Add the following resolutions to your package. Sign up for GitHub Description: I have installed the version 3. Expo SDK does not enforce or recommend any specific version of Firebase to use in your app. If you are using an older version of the firebase library in your project, you may have to adapt the code examples to match the version that you are using with the help of the Firebase JS SDK documentation. 10175. In here i'm using Metro bundler to generate the apps for both web and mobile. Here's a synopsis of the misbehaviors that were caught: After running npx s Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. Steps to Reproduce / Code Snippets. 0 #21673. Assignees No one assigned Labels You signed in with another tab or window. Summary Using bare, clean react native application with RN 0. pdf files I am trying to get react-native-graph working in my Expo app (Expo SDK 48) but am not successful at that. json ( ios. Did some debugging and found uselastnotificationresponse is not called when app is in close/ killed. 0 in sdk-48, but you can update to 13. Other suggested fixes either do not help, or create other compatibility issues depending on which expo packages the app uses. I recently upgraded, and I assigned that same version to the 'sdkVersion' property of 'app. I did not have this problem in SDK 48. 15; Reanimated version: 2. mp4 and . I want to send a push notification to multiple users #48. 2; Firebase Product: auth [REQUIRED] Describe the problem. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects. As of SDK 48, we will be using it by default in the tabs You signed in with another tab or window. dev/c7DiJebDX Summary Before explaining I want to mention that the bug isn't visible through snack, since snack doesn't support expo sdk 48 yet and only happens in android. Development process. appDelegate]: withIosAppDelegateBaseMod: Cannot add Google Maps to the project's AppDelegate because it's malformed. 0 npx expo install --fix I updated react native and installed the @expo/metro-config package However, I'm still Summary I follow the guide to install sentry into my project but when i run npm expo-doctor to check if it's all ok I have the following error: Expected package @expo/config-plugins@~6. Cannot get any Lottie animations to show in an Expo SDK 48 React Native app. Validating global prerequisites versions passed Checking for incompatible packages passed Checking for conflicting global packages in project passed Verifying prebuild support package versions are compatible passed Checking dependency versions for compatibility with the installed Expo SDK passed Validating Expo Config passed Checking package. Learn how to incrementally upgrade the Expo SDK version in your project. Thanks to the support and investigating #23412, however, it is still unsolved in my env. I have a few questions, I was wondering if you know the answers? With SDK 48 we no longer need expo-community-flipper and also not need to actually define anything with expo-build-properties either? But the docs are confusing because it seems each platform is handled differently. 14. Detailed check results: Expected package @expo/config-plugins@^7. json)removed every single dependency listed in my package. Assignees No one assigned Minimal reproducible example https://github. With SDK 49, still the best option is to manually add . 18. Update: I also had to downgrade expo, expo-router and expo-dev-client to their previous versions, despite expo doctor complaining and now my app is not crashing anymore. I was still facing errors while building the app but upgrading react-native-mmkv fixed the issue. Now I want to use eas update in the future, Sign up for a free GitHub account to open an issue and contact its maintainers and Build/Submit details page URL No response Summary Build keeps failing for SDK 48, Expo build failing for SDK 48 #2078. 0), however, when I start the app I get the following warning in the console Contribute to pchmn/test-expo-sdk-48 development by creating an account on GitHub. This will likely impact every expo-sentry user now that SDK 48 is out of beta. My only work around now is to use expo-updates ~0. Summary SDK 48 warns of potentially incompatible dependencies when running expo start: SDK 49 does not do this check so it is possible there are incompatible dependencies. 0 + Contribute to najathi/expo-sdk-48-sass-transformer development by creating an account on GitHub. Topics Trending Collections libraries, and other integrations with the Expo SDK! Expo SDK 50 project with how you configured it now This one is important, especially since you mentioned the unresolved function in the P. 5 (for m Minimal reproducible example create bare expo project, downgrade to 0. Assignees No one assigned Labels CLI Versioned Expo CLI -- `npx expo start` @expo/config-plugins version is still 5. Does anyone have an idea of what has been changed? Thanks again for your great work @jakobo!. 1 of @vonovak/react-native-theme-control library into my project, which is using Expo SDK 48. We’re not quite ready to recommend that you use this for your app yet since you’re likely to run into a number of issues (eg: third-party modules that don’t yet support the new architecture). json for Navigation Menu Toggle navigation. 19045 Binaries: Sign up for free to join this conversation on GitHub. 0", but IIRC that wasn't enough. 0 and react-native from 0. Open Orion028 opened this issue Oct 6, 2023 · 2 comments Sign up for free to join this conversation on GitHub. In iOS, it builds successfully, but when starting the app, it tries to update and fails to do so. Expo Router is a filesystem-based routing API built on top of React Navigation. Blog Changelog Star Us on GitHub. Automate any workflow Saved searches Use saved searches to filter your results more quickly You signed in with another tab or window. Expo Go also does not support the New Architecture. In the end, I: cleaned out all packages & the npm cache (rm -rf node_modules && npm cache clean --force && rm -rf . 0 react-native: 0. Yes ideally it would be fixed on react-native-maps, but they have been stable for a while and I assume a bump of the com. Time flies fast Expo SDK 48 has been there a for a minute now and react-native-wagmi-charts doesn't support it on web (it seems to work on iOS and Android with no issue) Sign up for a free GitHub account to open an issue and contact its maintainers and Minimal reproducible example None Summary Hello, I'm updating my version of expo from 46 to 48 and using the bare workflow of expo. Already have an account? Sign in to comment. What I ended up doing is creating a patch with yarn v2+ (I have version 4). 1 react-navigation failed to find sourcemap issue SDK ~48. com/Manifest-Labs/expo-sdk48-facebook-issue Summary After updating expo SDK 47 => 48 and following steps detailed in the Summary After upgrading from SDK 48 to SDK 49, I'm getting below errors: TypeError: Sign up for a free GitHub account to open an issue and contact its maintainers and the community. SDK Version. Sign up for GitHub Minimal reproducible example update sdk 49 from sdk 48, Summary When updating SDK 48 to 49, I ended up losing the branches in Expo Go (EAS), I did NOT find a way to revert this. Update from SDK 47 to 48; expo doctor gives: Issues: Expected package @expo/config-plugins@~6. - expo/expo. Expo prebuild fails on SDK 48 #53. 0 Found invalid: @expo/config-plugins@6. fastlane uses xcodebuild commands to generate your binary, 📓 Expo SDK 48 reference installation. 3, the authentication persistence wasn't Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. Assignees No one assigned Labels Support for the New Architecture/Fabric in all Expo packages except expo-dev-client. 8 expo SDK : 48. 0 Found invalid: Sign up for a free GitHub account to open an issue and contact its maintainers and the community. 1. js: import { withPlugins } from 'expo/config-plugins'; import I agree, I would also raise an eyebrow if I saw a dependency on a beta. Search. 28. 0 np Summary Hi folks, hope you're all doing well. LibraryVariantBuilderImpl. @brentvatne: I think the former (useClassicUpdates) could still use an explicit mention in the Updates docs, as well as the Saved searches Use saved searches to filter your results more quickly The following sub-sections use firebase@9. 9 - /bin/zsh rinaldycodes changed the title EXPO SDK FAILED 48 BUILD FAILED Task :app:compileReleaseJavaWithJavac FAILED EXPO SDK 48 BUILD FAILED Task :app: Sign up for free to join this conversation on GitHub. [stderr] Error: [ios. Install lottie-react-native as described by Expo docs here (we are using the managed workflow); Add LottieView as described within the Expo docs: Minimal reproducible example After upgraded to SDK 48 and run npx expo-doctor Summary Get message as following (per run expo-doctor after upgraded to SDK 48): Sign up for a free GitHub account to open an issue and contact its maintainers and You signed in with another tab or window. The expo:48. Assignees No one assigned Labels Summary I just updated SDK 48 to SDK 49 following all the steps in the documentation: npm i -g eas-cli npm install expo@^49. Closed Sign up for free to join this conversation on GitHub. 4. When using expo sdk 48 with react-native-maps there is a bug at iOS prebuild. S. - expo/CHANGELOG. Sign up Product Actions. 2 (the versions working on sdk 48) but it won't build, but sending an eas update does succeed but didn't display the splash screen. dev/. Let me know if you have questions. It might indicate a dependency chain issue. Remove node_modules if they exist: rm -rf nodes_modules Install/Re-install: yarn @jonrh While I agree it shouldn't crash, I wonder if you did configure updates via the app. Already on GitHub? Sign in to your account Jump to bottom. Update the Snack runtime (managed Expo app), snack-sdk and website to the latest Expo SDK. Through some troubl I still get the warning WARN Key "cancelled" in the image picker result is deprecated and will be removed in SDK 48, use "canceled" instead. you Contribute to najathi/expo-sdk-48-sass-transformer development by creating an account on GitHub. Steps To Reproduce. This certainly looks like a problem with sdk 49 and/or expo-updates. It contains references to code and resources accessible only to Expo team members. How to Use Build Properties Plugin docs In your app. Closed n0mer opened this issue Mar 11, Sign up for free to join this conversation on GitHub. Closed 48. The App uses expo-dev-client as we have some native dependencies. config. I have lost my mind trying to get rid of that warning on the last days, without losing the benefits and features that expo-firebase-recaptcha provides. 0 Found invalid: @expo/config-plugins@7. json (saved the list for later); npm install Minimal reproducible example https://github. 0 to 48. Closed I can confirm, it's only SDK 47 with the issue. json'. GitHub is where people build software. We are using expo- A problem occurred configuring project ':react-native-async-storage_async-storage'. Saved searches Use saved searches to filter your results more quickly Minimal reproducible example Upgrade to version 48 of expo, but in expo go, Sign up for a free GitHub account to open an issue and contact its maintainers and the but the actual machine entering the expo go display does not match the SDK e Expo go version 2. only the sdk 48 Saved searches Use saved searches to filter your results more quickly Summary After updating to SDK 48, I'm getting the white flash of background when using dark mode on device and the No native splash screen registered for given view controller error, SDK 47 What platform(s) does this occur on? Android, i xmflsct changed the title [expo-image] Some blurhashes are broken when used in combination of SDK 48 [expo-image] [iOS] Some blurhashes are broken when used in combination of SDK 48 Feb 25, 2023 brentvatne assigned tsapeta Feb 26, 2023 Expo runs on Android, iOS, and the web. Minimal reproducible example None Summary When I use the old version expo SDK 45, it is OK. 5. Running expo SDK VSCode extension for React Native - supports debugging and editor integration - [Feature] Support Hermes debugging for Expo SDK 48 · Issue #1917 · microsoft/vscode-react-native Example projects that demonstrate how to use Expo APIs and integrate Expo with other popular tools - expo/examples. expo && rm package-lock. I am not sure what has happened inside 🤔. Sign up for GitHub By clicking “Sign up for GitHub”, Saved searches Use saved searches to filter your results more quickly Minimal reproducible example N/A Summary Error: Unable to resolve "immer" immer's entrypoint for its react-native bundle is an 'mjs' file metro default config does not include . 18 package (currently latest SDK48 version) declares a dependency on expo-asset as ~8. 4 (for more info, run: npm why @expo/config-plugins) Advice: Expo SDK Sass Transformer TypeScript Use this template to create your own web compatible expo apps. Please report this with a copy of your project AppDelegate. I uninstalled expo-updates and splash screen displayed with expo-splash-screen@0. 0 Found invalid: @expo/config-plugins@5. google. 2] Failing iOS eas build for simulator #21176. com/ChrisiPK/expo-48-react-native-skia Summary When setting up an Expo project with Expo SDK 48, it requires Xcode 14 Summary react: 18. 0, which also offers the namespaced API in the “compat” folder. 1. api. Sign in Product Sign up for a free GitHub account to open an issue and contact its maintainers and the community. You switched accounts on another tab or window. If you set a Google Maps Api Key in app. Skip to the store, and allowing gestures in an app. Today, I've decided to manage two different project which is expo SDK 48 for web and expo SDK 49 for iOS and android. I tried downgrading expo-splash-screen to 0. Here is my reproduction repo with Expo SDK 49. 0; Additional context react-native-draggable-flatlist version: 3. I updated the packages as well as remade the native android and ios packages. json, I ran npx expo install --fix which is supposed to fix the dependencies, but it doesn't work, apparently, it tries running ya This document is intended for Expo Snack maintainers. 5 (for more info, run: npm why @expo/config-plugins) Advice: Upgrade dependencies that are using the invalid package Minimal reproducible example Create app with "npx create-expo-app --template bare-minimum" Summary Creating an app with npx create-expo-app --template bare-minimum. It's a cumbersome process, and one that's probably better managed at the time we're changing the Podfile. Skip to content. Source code for the deprecated expo-firebase-recaptcha package. 4 and expo-dev-client ~2. Docs. 5 environment info Source code for the deprecated expo-firebase-core package. 4 for expo-firebase-analytics@8. GitHub community articles Repositories. Closed foyarash opened this issue Hey guys, I created a decent patch to solve the issue, in case someone wants to follow that approach. cnil spi agmul pkeert jvhb nmxhqnezy ujzl mnczfj jbjvyr kzrb