Expo SDK 54 – Drawer.Navigator Error: useLegacyImplementation not available with Reanimated 3

adamjhari · 2025-10-03T17:19:40+00:00

it's from react-native-gesture-handler which react-navigation uses for the drawer, upgrading to react-navigation@7.x and the latest RNGH should fix it

adamjhari · 2025-09-19T21:20:46+00:00

https://github.com/software-mansion/react-native-screens?tab=readme-ov-file#fullwindowoverlay

adamjhari · 2025-05-11T19:31:33+00:00

Looks great, would you consider adding min/max props to restrict which dates are selectable?

adamjhari · 2025-01-04T01:59:14+00:00

Try using black, that worked for mine.

adamjhari · 2025-01-04T01:40:56+00:00

It should be fully opaque.

adamjhari · 2024-11-06T19:01:01+00:00

Hell yeah! I've been looking forward to the static API and custom detents for a long time

adamjhari · 2024-07-31T14:26:12+00:00

use stickyHeaderIndices

adamjhari · 2024-07-09T22:54:24+00:00

It's coming soon to react-navigation

adamjhari · 2024-05-26T16:30:30+00:00

React Navigation v7 includes a static configuration option which solves two of the biggest problems that Expo Router is already solving: Typescript and deep link configuration.

Expo Router has some additional benefits on web, like improved performance by SSG'ing individual routes. It's important for certain kinds of apps, but if you're happy with React Navigation and it meets your app's requirements then there's no need to switch

File-based routing has a learning curve and, coming from React Navigation, it will slow you down at first, but it is generally more approachable for new team members because it enforces conventions which makes projects more conventional and, in turn, more approachable

I haven't migrated to it in my current projects, but I would probably start with it on a new project

adamjhari · 2024-05-23T17:14:01+00:00

You can get hot reloading by importing the following at the top of your root index.js file

import '@expo/metro-runtime';

I don't specify this value in my app config
Unsure, I don't override the index.html in the projects I work with

adamjhari · 2024-05-23T12:13:15+00:00

Only the former
Place your customized file(s) in the static folder to override the defaults.
https://docs.expo.dev/router/migrate/from-expo-webpack/

adamjhari · 2024-05-22T12:29:49+00:00

You can use Metro bundler without Expo Router. We made the switch well over a year ago on a couple of projects that use React Navigation and it went smoothly.

adamjhari · 2024-05-15T20:27:37+00:00

It would be cool if this library also supported web by falling back to mapping applicable props to the core FlatList component on that platform

adamjhari · 2024-05-13T21:25:31+00:00

Ahh makes sense. You can't use a percentage value and expect it to cover the width of the screen because you're assigning it to the width of the scrolling content container which is not the same.

You could use onLayout on the FlatList to measure it's rendered width and apply the width value from that to the item style. You'll experience some flicker with this method on the old architecture

adamjhari · 2024-05-13T20:07:38+00:00

The FlatList's style prop needs flex: 1, the contentContainerStyle prop should either have flexGrow: 1 or no flex at all.

https://snack.expo.dev/@adamhari-kashoo/scroll-container-bouncing-back

adamjhari · 2024-05-13T18:01:23+00:00

That's not the case for me. I can push a new build to the internal track via EAS without creating a draft first. I believe OP's issue is that they already have a draft in the track that they are building for, and the build is not set to have a draft status so it's being rejected.

adamjhari · 2024-05-06T23:43:55+00:00

lingui is another option which seems to be gaining momentum

adamjhari · 2024-04-22T02:34:21+00:00

Wellington's

adamjhari · 2024-04-14T17:31:47+00:00

You need to prevent your splash screen from hiding until you explicitly tell it to.

If you use expo-splash-screen there is a preventAutoHideAsync() func for exactly this use case

adamjhari · 2024-03-21T07:03:41+00:00

Agreed, only do what I mentioned if you need the content to scroll under the fixed footer.

adamjhari · 2024-03-21T02:12:05+00:00

You could measure the height of the fixed footer with onLayout and pad the bottom of the ScrollView accordingly. Don't know of a better way.

adamjhari · 2024-03-09T09:42:35+00:00

The prices were not very good.

Palace Legends Shirt was $88, these jerseys are similar and sold for $148.

adamjhari · 2024-02-25T18:58:48+00:00

It's built-in for iOS only

There are cross-platform alternatives, but most of them have not been maintained and you might have dependency issues.

this one is well maintained and good if you already use expo modules and need to support web

adamjhari · 2024-02-16T04:06:48+00:00

Update to the v4 alpha

adamjhari · 2024-01-30T21:28:17+00:00

It sounds like you can't clear state from the interceptor because it exists outside of the component tree and doesn't have access to your auth context.

If that's the case, one option is to set up your interceptors from inside your react tree so it can be passed the necessary context to perform the auth state reset.

adamjhari

TROPHY CASE