expo VS fyi

I am using expo setup with tabs template.

Before we begin working on our project, we must set it up and install all the necessary dependencies. We will be using Expo for this project. Expo is a React Native management tool that handles a lot of heavy stuff for us, such as efficiently compiling code and assets, as well as provides us with a productive development environment. Also we will be using Typescript for this project, but don't worry, the process is practically identical to Javascript, so if you don't know Typescript that's fine. This article assumes some basic understanding of React and React Native , such as components, hooks and state. You must also have Node.js installed on your computer.

Expo saves us from the complex configurations required to create a native application with the React Native CLI, making it the easiest and fastest way to build and publish React Native apps.

- Try to unblock usage of Google Maps in my ReactNative Android, iOS and Web App. Context: "https://github.com/expo/expo/issues/23347#issuecomment-16264...

- Provide financial report to investors (this will likely take at least two blocks)

- Fix initial Zoom setting for Google Maps in my app for web. Context: https://github.com/teovillanueva/react-native-web-maps/issue...

- Check on analytics + user enqueries and write (back) to at least 3 of our most active users in the last couple of days

Timeblock exhausted. Posting this and jumping on first task from above.

But some bugs don't get fixed for years. E.g. there was an issue with expo-secure-store not working well on android after app reinstallatiins. It apparently got fixed now 5 years after it was reported: expo-secure-store bug

So i found out this client was using unimodules for a lot of his libraries. But unimodules has been deprecated and merged into expo now. So now I followed the instructions here, and it looks like I just have migrated my application into expo only as it(expo-upgrade) created created a .expo folder now and also bumped package.json libraries to latest versions.

TLDR - Released new updates on EAS Update branch promotion flow deployment pattern to use a separate channel for each production runtime version release build: https://docs.expo.dev/eas-update/deployment-patterns/#branch-promotion-flow - Updates from Expo Modules API getting started guide: When importing a module in your app, you can now use relative paths: https://docs.expo.dev/modules/get-started/#using-the-module. You can still use absolute paths to import the module when creating it locally by using an additional configuration: https://github.com/expo/fyi/blob/main/absolute-path-expo-modules.md - EAS Build serves most dependencies & CocoaPods artifacts from a cache server for Android & iOS. However, in your project if you've ios directory & want cache Podlock.lock you can use paths property in eas.json: https://docs.expo.dev/build-reference/caching/#ios-dependencies - You can always look into EAS Build server infrastructure doc to learn more about the current configurations for Android and iOS build servers: https://docs.expo.dev/build-reference/infrastructure/ - With expo-updates, you can always check for updates manually if they are working or not. Check out the example: https://docs.expo.dev/versions/latest/sdk/updates/#check-for-updates-manually - Hermes apps use this debugging technique automatically when you open the debugger in Expo Go or a development build. For more in-depth info about check out the section on remote debugging: https://docs.expo.dev/guides/using-hermes/#can-i-use-remote-debugging-with-hermes - To add expo-updates to an existing React Native project, you need to configure your project. We recently updated the guide that works with latest React Native version: https://docs.expo.dev/bare/installing-updates/

I followed the instructions here: https://github.com/expo/fyi/blob/main/firebase-migration-guide.md

I got the DevicePushToken and sending APN push notification in the backend with Node, but I just couldn’t get it work in Expo (managed workflow). I followed exactly in docs which poorly documented and I also tried exactly like this.

Has anyone had success with this tutorial from Expo? We've followed the steps here (https://github.com/expo/fyi/blob/main/creating-google-service-account.md), but in Step 8 ("Return to the API access page on the Google Play Console and ensure it shows your new service account. Click on Grant access for the newly added service account.") the service account just isn't listed.

This will create a prebuilt Expo app. That is, you'll see ios and android folders in your project and this won't be a managed Expo app, where all the native details are hidden and Expo takes care of everything. Having said that, you don't need to go into the ios or android folders unless you need to add some native code in Swift or Kotlin.

Right now, Realm is not compatible with Expo Managed Workflows. In a managed Workflow Expo hides all iOS and Android native details from the JavaScript/React developer so they can concentrate on writing React code. Here, we need to prebuild our App, which will mean that we lose the nice Expo Go App that allows us to load our app using a QR code.

The smaller bundle size is also being worked on. Not quite sure what their timeline is, but I think it's pretty soon? See here: https://github.com/expo/fyi/blob/master/managed-app-size.md and/or watch this: https://www.youtube.com/watch?v=7E6zsRpfT4U