Closed mrflip closed 3 years ago
Yarn.lock file: https://gist.github.com/mrflip/3c0ca8931cee0fae1784b7bee902c898
I'd welcome advice for how to better create a minimal breaking example.
The error persists on a fresh clone of my repo, creating a brand-new yarn.lock and node_modules folder, into a wiped ios simulator device. Toggling between v12 and v10 toggles the brokenness on or off.
we don't import date picker in this repo at all, i'd try checking your node_modules to see where that's coming from
After upgrading to expo 40 and thus @expo/vector-icons 12.0.x, my app fails at startup on iOS with "Native Module cannot be null". It works in react-native-web, and it works immediately if I pin e/v-i back to version 10.2.1. I tried to create a minimal test case by installing a blank app and replacing with my package.json but could not reproduce. I've attached the package.json and call stacks.
Not sure if this is the problem, but the create-icon-set code eventually leads to a file that re-exports
*
from react-native; I'm wondering if this is causing react-native to then bundle in every single thing that it could possibly export, triggering the warnings and errors seen below.I used yarn why and grepped through things and can't find any evidence that my code or dependencies are requesting any kind of date picker or iOS notifications.
Stack trace from LogBox:
This trace is more detailed than what the console log shows, not sure why.
Stack Trace:
package.json