Germán Pineda

hmm yeah that was my first intuition so I checked our `yarn.lock` to see if it was included in any other dependencies and nothing found 😕 here's the output of...

We're developing our expo app in an Nx monorepo along side other bare bones react native apps and this crash started happening once we upgraded `react-native` from `0.72.6` to `0.72.9`....

@robcaldecott could you share what version of `expo` and `expo-notifications` you're on? I've tried using the `notification` settings and/or the `expo-notifications` plugin settings and none seem to fix the problem...

@robcaldecott are you only relying on locally scheduled notifications? For us, it seems locally scheduled notifications show the icon but when we send them remotely via [expo push notification tool](https://expo.dev/notifications)...

same issue here, would mean a ton if someone found a solution a could post it here 🙏

> Delete the symlinked node_module folder and link it again. Don't forget to reinstall pod. That didn't work for me. For some reason, my issue was related to `react-native-track-player: 4.0.0-rc6`....

The fix was released in `8.0.0`: https://github.com/microsoft/react-native-code-push/releases/tag/v8.0.0

We started seeing this crash as well after migrating from `react-native-splash-screen` to `react-native-bootsplash`: 

In my case `yarn` already executes `yarn dedupe` automatically so that didn't solve the problem. What solved the problem for me was forcing the resolution in my `package.json` like so:...

Seeing the same issue as well - any updates here?