Invalid Hook Call with >=v1.4.18

I am running an iOS (non-web) app on dripsy v1.4.17 but when I upgrade to v1.4.18 or v1.15.16 I get the following error:

[1]  | [0]  WARN  RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks
[1]  | [0]  ERROR  Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
[1]  | [0] 1. You might have mismatching versions of React and the renderer (such as React DOM)
[1]  | [0] 2. You might be breaking the Rules of Hooks
[1]  | [0] 3. You might have more than one copy of React in the same app
[1]  | [0] See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
[1]  | [0] 
[1]  | [0] This error is located at:
[1]  | [0]     in ThemeProvider (at provider/index.tsx:33)
[1]  | [0]     in DripsyProvider (at App.tsx:49)
[1]  | [0]     in ApolloProvider (at App.tsx:48)
[1]  | [0]     in App (at renderApplication.js:47)
[1]  | [0]     in RCTView (at View.js:34)
[1]  | [0]     in View (at AppContainer.js:107)
[1]  | [0]     in RCTView (at View.js:34)
[1]  | [0]     in View (at AppContainer.js:134)
[1]  | [0]     in AppContainer (at renderApplication.js:40)

Was there something that changed significantly between these two patch-level versions? Any ideas as to what is causing this?

[JackCA]

No I cannot. Apologies for the noise.

It looks like this was a yarn workspace issue that I spent quite a bit of time tracking down. I ended up upgrading to yarn 2 and using noHoistingLimits and now no longer have any react-native special-casing for workspaces which is win-win.

[JackCA]

Could you elaborate on 1? I’m not exactly familiar with what hoisting is (or how metro works) but I’d be really interested in solving this.

I was using a vanilla react-native app so I don’t think you can use expo-yarn-workspaces with one (I tried at least). I also tried https://www.npmjs.com/package/react-native-yarn-workspaces-v2 which didn’t work either. There were hacks I had to do to make react-native pick up the correct directories and such.

Was upgrading to yarn 2 an issue?

Not at all in my situation. It’s the second time I’ve upgraded and I’ve been really happy with it. I followed this guide .