@magicbell/react-headless does not work on new versions of Expo/React Native

[dentep]

I have just updated expo SDK from 47 to 51 and also updated MagicBell package. The notifications hook does work anymore in the new versions and produces warnings...

package.json:

"dependencies": {
    "@config-plugins/react-native-blob-util": "^8.0.0",
    "@config-plugins/react-native-pdf": "^8.0.0",
    "@freakycoder/react-native-bounceable": "^1.0.3",
    "@magicbell/react-headless": "^4.5.6",
    "@notifee/react-native": "^7.8.2",
    "@react-native-async-storage/async-storage": "1.23.1",
    "@react-native-firebase/app": "^17.4.2",
    "@react-native-firebase/dynamic-links": "^17.4.2",
    "@react-native-firebase/messaging": "^17.4.2",
    "@react-navigation/bottom-tabs": "^6.4.0",
    "@react-navigation/drawer": "^6.5.0",
    "@react-navigation/elements": "^1.3.6",
    "@react-navigation/native": "^6.0.13",
    "@react-navigation/native-stack": "^6.9.17",
    "@react-navigation/stack": "^6.3.4",
    "@reduxjs/toolkit": "1.8.5",
    "@sentry/react-native": "~5.22.0",
    "@types/react": "~18.2.79",
    "@types/react-native": "~0.70.6",
    "@typescript-eslint/parser": "^8.2.0",
    "axios": "^1.7.4",
    "dayjs": "1.11.5",
    "deprecated-react-native-prop-types": "^5.0.0",
    "expo": "^51.0.30",
    "expo-application": "~5.9.1",
    "expo-build-properties": "~0.12.5",
    "expo-clipboard": "~6.0.3",
    "expo-constants": "~16.0.2",
    "expo-dev-client": "~4.0.24",
    "expo-device": "~6.0.2",
    "expo-image-picker": "~15.0.7",
    "expo-linking": "~6.3.1",
    "expo-modules": "^0.0.0",
    "expo-modules-core": "~1.12.22",
    "expo-network": "~6.0.1",
    "expo-notifications": "~0.28.16",
    "expo-status-bar": "~1.12.1",
    "expo-updates": "~0.25.23",
    "i18next": "21.9.2",
    "linkify-it": "4.0.1",
    "mixpanel-react-native": "^2.3.1",
    "normalizr": "3.6.2",
    "pods": "2.0.0",
    "prop-types": "15.8.1",
    "react": "18.2.0",
    "react-devtools": "^4.27.2",
    "react-dom": "18.2.0",
    "react-i18next": "11.18.6",
    "react-native": "0.74.5",
    "react-native-blob-util": "^0.19.11",
    "react-native-gesture-handler": "~2.16.1",
    "react-native-hyperlink": "0.0.22",
    "react-native-keyboard-accessory": "0.1.16",
    "react-native-keyboard-aware-scrollview": "2.1.0",
    "react-native-pager-view": "6.3.0",
    "react-native-paper": "^5.8.0",
    "react-native-pdf": "^6.7.5",
    "react-native-poll": "0.1.2",
    "react-native-read-more-text": "^1.1.2",
    "react-native-reanimated": "~3.10.1",
    "react-native-render-html": "^6.3.4",
    "react-native-safe-area-context": "4.10.5",
    "react-native-screens": "3.31.1",
    "react-native-share": "7.9.0",
    "react-native-svg": "15.2.0",
    "react-native-tab-view": "^3.5.2",
    "react-native-url-preview": "^1.1.9",
    "react-native-vector-icons": "9.2.0",
    "react-native-web": "~0.19.10",
    "react-native-websocket": "^1.0.2",
    "react-native-webview": "13.8.6",
    "react-redux": "8.0.4",
    "reactotron-react-native": "^5.0.3",
    "reactotron-redux": "^3.1.3",
    "redux": "4.2.0",
    "redux-persist": "6.0.0",
    "route-recognizer": "^0.3.4",
    "sentry-expo": "~7.0.0",
    "typescript": "~5.3.3"
  },

provider:

MagicBellProvider
      apiKey={MAGICBELL_API_KEY}
      userExternalId={<user_id_here>}
      userKey={<user_key_here>}
      stores={[<stores_here>]}
    >
      {children}
    </MagicBellProvider>

using the hook useNotifications does not return any notifications anymore : const { isEmpty, notifications } = useNotifications(currentFilter)

trying to run useNotifications produces following error:

[smeijer]

Hey @dentep ,

I don't have a solution for you right now, but an error like this sounds like a change in your (probably expo's) build setup, which now triggers an cjs/esm issue when importing from immer (our dependency).

It might be that they already have a solution for compatibility issues like these.

[dentep]

can you tell me which direction should i look? seems like only downgrading expo is a possible (but not preferred) solution at this point...

[unamashana]

@dentep Unfortunately, that'd definitely be the quickest way. Are you losing any functionality downgrading Expo?