Any way to detect memory leaks in expo without using profiler, just easy as leakCanary

Moved from: https://github.com/expo/expo/issues/11 Add support for in app purchases to standalone apps on iOS and Android in the managed workflow Status as of May 3, 2021: We are working on supporting native plugins in Expo managed apps, you can read about it here: https://blog.expo.io/expo-managed-workflow-in-2021-d1c9b68aa10 - but it's not ready yet. ------------------------------ Status as of July 21, 2020: The same as the previous status update applies here. We are still building the infrastructure that we need to be able to support IAPs in the managed workflow. If you need them, I recommend ejecting to the bare workflow. You can continue to use all of the Expo SDK packages after ejecting, including OTA updates and Notifications. https://docs.expo.io/workflow/customizing/ ------------------------------ Status as of April 14, 2020: IAP APIs in the managed workflow will not be available until we have completed support for native plugins in the managed workflow, which is part of our rewrite of the build service. You may want to consider using bare workflow for now! You can continue to use Updates and Notifications in bare React Native apps now as of SDK 37: https://blog.expo.io/expo-sdk-37-is-now-available-dd5770f066a6 . ------------------------------ Status as of November 7, 2019: This feature is definitely important for us in the medium to long-term but we need to build some more infrastructure before it's possible. We're currently rewriting our build service to make it capable of handling adding In-App Purchase support to apps but it's not there yet.

https://github.com/expo/expo/discussions/20975 https://github.com/reactwg/react-native-new-architecture/discussions/105 tl;dr: From React Native 0.71, you will consume prebuilt artifacts on Android (and iOS to some degree) coming from Maven Central. This brings huge improvements in terms of build time for the New Architecture (and not only, keep on reading!)

https://github.com/passwordless-id/connect is using the new safari thing where it can auth a user using face id, touch id, etc. https://dev.to/dagnelies/passwordless-authentication-for-your-website-in-5-minutes-1c31 heres a good example of it. PS. its still not a production ready thing.

We need this feature for both of the platforms. This is an essential feature. Expo must add this to its' built-in modules: https://github.com/alinz/react-native-share-extension [1] https://developer.android.com/training/sharing/send [2] https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Share.html#//apple_ref/doc/uid/TP40014214-CH12-SW1

The Production plan is too expensive for my personal projects but I would gladly pay for a cheaper Personal plan that gives a couple priority builds per day.

Allow to set an alternative splash screen color and image when device is set to dark mode. If it is possible to customize the status bar the same way would be brilliant.

Some way to support building smartwatch apps.

Branches should be ordered by the date of the most recent update, not by the branch's creation date. Currently if you make updates to an old branch, it stays at the bottom of the list. My team keeps historical versioned release branches, but we also have a persistent staging branch. However, the staging branch gets buried over time under the release branches, even after making updates.

Only one favicon is currently supported. However it's normal to have 4 or more to support different browsers. https://docs.expo.dev/versions/latest/config/app/#favicon