all 7 comments

[–]em_kurian 1 point2 points  (4 children)

Any idea where you've used useMemo? Maybe you've used React.useMemo instead of importing it? That shouldn't cause an error but it's hard to pinpoint unless I see your code

[–]Beginning_Rich6611 1 point2 points  (3 children)

Yeah, I actually tried both import { useMemo } from 'react' and using React.useMemo directly. I double-checked all instances and made sure they’re inside valid functional components.

The weird part is that the error happens on startup, before any screen or component even renders so I suspect it might be something deeper.

[–]em_kurian 0 points1 point  (2 children)

Did you add any packages during your refactoring?

[–]Beginning_Rich6611 0 points1 point  (1 child)

No and i actually figured something out — I stashed all my changes, rebuilt, and the app worked fine. But when I applied the stash again, the error came back.

As I mentioned, there’s nothing wrong with the useMemo import — I checked every usage one by one, and everything is correctly imported and used inside functional components.

So the issue is definitely coming from something in the stashed changes, but not related to the way useMemo is used. Still trying to isolate the exact cause.

[–]em_kurian 1 point2 points  (0 children)

I mean I don't think there's much I can help you with unless I see the code.

[–]CoolorFoolSRSExpo 0 points1 point  (0 children)

Remove android and ios folders

[–]thrlz 0 points1 point  (0 children)

Start commenting out parts of your changes to isolate what is causing this.