Frequently Asked Questions

A curated summary of the top questions asked on our Slack community, often relating to implementation, functionality, and building better products generally.
Statsig FAQs
bloomberg Brex Microsoft Notion Univision Webflow bluesky vercel Rippling ea OpenAI Flipkart
GENERAL

How can I resolve a dependency conflict between `expo-device` and `@statsig/expo-bindings` in my Expo 51 project?

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.

Join the #1 experimentation community

Connect with like-minded product leaders, data scientists, and engineers to share the latest in product experimentation.

Try Statsig Today

Get started for free. Add your whole team!

Why the best build with us

OpenAI OpenAI
Brex Brex
Notion Notion
SoundCloud SoundCloud
Ancestry Ancestry
At OpenAI, we want to iterate as fast as possible. Statsig enables us to grow, scale, and learn efficiently. Integrating experimentation with product analytics and feature flagging has been crucial for quickly understanding and addressing our users' top priorities.
OpenAI
Dave Cummings
Engineering Manager, ChatGPT
Brex's mission is to help businesses move fast. Statsig is now helping our engineers move fast. It has been a game changer to automate the manual lift typical to running experiments and has helped product teams ship the right features to their users quickly.
Brex
Karandeep Anand
President
At Notion, we're continuously learning what our users value and want every team to run experiments to learn more. It’s also critical to maintain speed as a habit. Statsig's experimentation platform enables both this speed and learning for us.
Notion
Mengying Li
Data Science Manager
We evaluated Optimizely, LaunchDarkly, Split, and Eppo, but ultimately selected Statsig due to its comprehensive end-to-end integration. We wanted a complete solution rather than a partial one, including everything from the stats engine to data ingestion.
SoundCloud
Don Browning
SVP, Data & Platform Engineering
We only had so many analysts. Statsig provided the necessary tools to remove the bottleneck. I know that we are able to impact our key business metrics in a positive way with Statsig. We are definitely heading in the right direction with Statsig.
Ancestry
Partha Sarathi
Director of Engineering
We use cookies to ensure you get the best experience on our website.
Privacy Policy