## TL;DR

Use your Client SDK key (dvc_client...), which the reporter confirmed fixed it. Check your version of DevCycle first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

## Steps

1. [leslie-lau (contributor)]: The DevCycle React Native SDK only accepts keys that start with client or dvc_client, so a Mobile SDK key will not work. Use your Client SDK key (dvc_client...), which the reporter confirmed fixed it.

2. This comes from one real issue thread (https://github.com/DevCycleHQ/js-sdks/issues/1151); it is the verified fix or approach from that thread, not a general manual. Check your version of DevCycle first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

## When to use

You are seeing this: Issue DevCycleHQ/js-sdks#1151 (closed, 7 comments): ## Description ## DevCycleProvider failed to initialize when used in React Native Expo with expo-router even if the correct sdkKey was given ## Error Message ## ``typescript [React] { [UserError: Invalid... Use this skill when you run into "UserError: Invalid SDK key provided. Please call initialize with a valid client SDK key".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

Issue DevCycleHQ/js-sdks#1151 (closed, 7 comments): ## Description ## DevCycleProvider failed to initialize when used in React Native Expo with expo-router even if the correct sdkKey was given ## Error Message ## ``typescript [React] { [UserError: Invalid SDK key provided.

## Sources

- YOUR_YOUR_HOST

- https://github.com/DevCycleHQ/js-sdks/issues/1151