Can't install Pods when using pnpm

[itajenglish]

SDK version: 4.2.1

Environment: Development

Are logs available?

⚠️  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: There are multiple dependencies with different sources for `customerio-reactnative` in `Podfile`:

- customerio-reactnative (from `../node_modules/customerio-reactnative`)
- customerio-reactnative/apn (from `../node_modules/.pnpm/customerio-reactnative@4.2.1_react-native@0.74.5_@babel+core@7.26.7_@babel+preset-env@7_06e540787e821bc5aa9d6cc4e047b81d/node_modules/customerio-reactnative`)

pod install --repo-update --ansi exited with non-zero code: 1

Describe the bug
Can't install using pnpm due to dependency issues

To Reproduce

• Run pnpm add customerio-reactnative@4.2.1
• Run npx expo prebuild --clean or cd ios && pod install

Expected behavior

• Should install without issue

Screenshots

Additional context
This works using npm or yarn

[itajenglish]

node-linker=hoisted
shamefully-hoist=true
public-hoist-pattern[]=*customerio*

Adding this to an npmrc file seems to fix the issue but we would prefer not to have to do this as that file gets rewritten in or CI/CD pipeline

[Shahroz16]

Hey @itajenglish, thank you for flagging this. We don't officially support pnpm yet, I have added a feature request to ensure our package is compatible with pnpm. We are going to update the status of the ticket as soon as we start on it. Thank you for your patience and understanding.

[walkev13]

I have the same issue on my end, it would be great if it could be resolved 🙏

[itajenglish]

👀 Is there any updates on this?

[mahmoud-elmorabea]

Hi folks,

Apologies for lack of updates here!

I created a pull request that should enable usage of pnpm without any config or hoisting behavior required.

Is that something you'd wanna try out @itajenglish @walkev13 ? 😇

You can use git branch to pull the Expo plugin instead of a version, branch-> pnpm-support-fix . You can use it as such, in your package.json

"dependencies": {
  ...
  "customerio-expo-plugin": "github:customerio/customerio-expo-plugin#pnpm-support-fix"
  ...
}

Be sure to delete all existing artifacts first:

rm -rf node_modules
rm package-lock.json
rm yarn.lock
rm pnpm-lock.yaml

I am trying to validate the fix works for an environment like yours before cutting a release. Hope this works more straightforward for you!

[itajenglish]

Hi folks,

Apologies for lack of updates here!

I created a pull request that should enable usage of pnpm without any config or hoisting behavior required.

Is that something you'd wanna try out @itajenglish @walkev13 ? 😇

You can use git branch to pull the Expo plugin instead of a version, branch-> pnpm-support-fix . You can use it as such, in your package.json

"dependencies": {
  ...
  "customerio-expo-plugin": "github:customerio/customerio-expo-plugin#pnpm-support-fix"
  ...
}

Be sure to delete all existing artifacts first:

rm -rf node_modules
rm package-lock.json
rm yarn.lock
rm pnpm-lock.yaml

I am trying to validate the fix works for an environment like yours before cutting a release. Hope this works more straightforward for you!

Hey @mahmoud-elmorabea thanks for the follow up. We actually don't use Customer.io anymore or pnpm for that matter, we use Bun now. In any case good to know for future reference if things change.