Frequently Asked Questions

Date of slack thread: 6/20/24

Anonymous: I’m using:

"@statsig/expo-bindings": "^1.3.1",
"@statsig/js-client": "^1.3.1",

in my react native app.

We’re running a bare expo workflow and are on Expo version 51. I’m having an issue when running npm install. Here is the full log of the error:

Log files:
/Users/connormullins/.npm/_logs/2024-06-20T22_16_02_698Z-debug-0.log

# npm resolution error report

While resolving: omnia-fishing-rn@3.14.0
Found: expo-device@6.0.2
node_modules/expo-device
  expo-device@"~6.0.2" from the root project

Could not resolve dependency:
peer expo-device@"5.*" from @statsig/expo-bindings@1.3.1
node_modules/@statsig/expo-bindings
  @statsig/expo-bindings@"^1.3.1" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

I am currently resolving this locally by running npm install --force. It works, but is not a viable solution for our CI/CD pipeline, since it only runs npm install.

I was wondering whether it would be possible to release a new version of @statsig/expo-bindings that relies on expo-device@"~6.0.2" so Expo 51 compatibility is possible?

Statbot: It appears that you are encountering a dependency conflict between the version of expo-device that your project requires and the version that @statsig/expo-bindings expects as a peer dependency. The @statsig/expo-bindings package is looking for expo-device@"5.*", but your project is using expo-device@6.0.2.

Unfortunately, as an AI support rep, I cannot directly influence the release of new package versions. However, I can provide you with some debugging advice. You can try the following steps:

1. Check if there is a newer version of @statsig/expo-bindings that supports expo-device@"~6.0.2". If there is, you should update to that version.
2. If no such version exists, you can continue using npm install --force or npm install --legacy-peer-deps as a temporary workaround.
3. Reach out to the maintainers of @statsig/expo-bindings to request an update for Expo 51 compatibility. They may already be working on an update or can provide a timeline for when it might be available.

Remember to test thoroughly when using --force or --legacy-peer-deps to ensure that there are no runtime issues due to the mismatched peer dependency.

For now, you might also consider modifying your CI/CD pipeline to use the --legacy-peer-deps flag as a temporary measure until an updated version of @statsig/expo-bindings is available.