Performances differences DrawerNavigator vs using DrawerLayoutAndroid directly

[ferrannp]

I hope it will be noticeable in the gifs but there are noticeable differences between DrawerNavigator and using DrawerLayoutAndroid directly. With DrawerNavigator, it does not seem that fluid. Specially when swiping fast to close it, using DrawerLayoutAndroid closes much faster (as expected).

I also noticed that in DrawerNavigator, more or less 50% of the times, when I click outside of the drawer it does not response (when it should close).

I know that DrawerNavigator uses DrawerLayoutAndroid under the hood so not sure what might be causing this issue.

Using DrawerLayoutAndroid directly:

Using DrawerNavigator:

[st0ffern]

@ferrannp good catch!
I have the same problem, and think i have found the problem.

It seems like react-native-drawer-layout-polyfill returns the polyfill no matter if you are on android or not.
Overriding the component here with DrawerLayoutAndroid did fix the issue.
https://github.com/react-community/react-navigation/blob/master/src/views/Drawer/DrawerView.js#L127-L145

** update
It is a bug in react-native-drawer-layout-polyfill 1.2.0 version that does not load Android correct from the package.json (rnc-archive/react-native-drawer-layout-polyfill@3e3453a) .

Updating to react-native-drawer-layout-polyfill 1.3.0 will fix it.

I will make a PR 😉

[vonovak]

this is no longer an issue, I think

[st0ffern]

can confirm it is fixed.

[kelset]

This is fixed since PR #2568 (so in beta.13).

[st0ffern]

I am still experiencing this issue, any others doing that?