Luke Walczak

I guess the main purpose of `onPress` on the `FABGroup` is to handle the callback on the main `FAB` when stack is opened. Imo`onLongPress` should be an auxiliary option for...

Could you please provide some app examples when there is a long press functionality on the FAB button? We are still discussing that feature and direction in which to go.

Hey @fabriziocucci, I think that makes sense. Would you like to add the `loading` property to the `Searchbar` _(e.g. similarly to the one existing in `Button`)_ covered by the unit...

Solved by: https://github.com/callstack/react-native-paper/pull/3322

> Two general suggestions: > 1) Try to use custom jest matchers from `@testing-library/jest-native` these should allow you to make more high-level assertions > 2) Gradually migrate to use `screen`...

Hey @lucaswitch could you please present on the snack (since it's the easiest way to present the problem using different library versions) the difference in `TextInput` between the latest version...

Is that issue still valid? Wondering whether the reported bug is specific to the library or `react-native` in general.

It should work by passing `autoFocus` prop into `SearchBar` component, like presented on the [snack](https://snack.expo.dev/v479rSt-f)

You can try to reproduce your issue on the fresh `react-native` project, with the tech stack used in your project.

After the early investigation, I think the issue is related to the `Surface` shadow and `BottomNavigation` shifting animation on both theme versions MD2 and MD3.