I had the same issue, after bisecting since last successful build, it appears that the issue in my case was react-native-reanimated, reverting from 2.2.1 to 2.2.0 fixed the issue.
I had the same issue, after bisecting since last successful build, it appears that the issue in my case was react-native-reanimated, reverting from 2.2.1 to 2.2.0 fixed the issue.