Troubleshooting
init and add — when something fails at install time or the first run. For a blank project, start at Installation.Run doctor first
npx @expokit/cli@latest doctor checks components.json, the @/ alias, route layout and packages each installed item needs.
Wrong native versions
Pinning react-native or Reanimated by hand is the usual cause of Cannot find native module in Expo Go. Let the SDK decide:
npx expo install --checknpx expo install --fixnpx expo start --clearnpx expo-doctor also flags SDK mismatches in app.json and dependencies.Import alias
Components import from @/components/ui/…. If TypeScript or Metro cannot resolve @/, re-run npx @expokit/cli@latest init in your app root and confirm tsconfig.json has "paths": { "@/*": ["./src/*"] } (or ./ if you have no src/).
Kit version warning
add compares your KIT_VERSION in lib/kit.tsx with what newer components need. Run npx @expokit/cli@latest diff to see what changed upstream, merge by hand, or npx @expokit/cli@latest add kit --force and re-apply your edits. Details: Kit version.
Unable to resolve module
Each item installs only its own peers. If Metro says it cannot resolve react-native-svg (or similar), either run the install line from the component docs or:
npx expo install react-native-svgThen npx @expokit/cli@latest doctor again. See Installation → peer dependencies.
Works in dev but not Expo Go
Glass, Skia carousels, Map and some Liquid Glass pieces need native code Expo Go does not ship. The component page shows Dev build on the badge. Use npx expo run:ios / run:android or EAS — see Native & Expo Go.
Pro item will not download
Run npx @expokit/cli@latest login with a token from /account. In CI set EXPO_KIT_TOKEN. A 403 usually means the item is Pro and the token is missing or expired.
Something else
Open a thread on Support with your Expo SDK version, the output of npx @expokit/cli@latest doctor, and the exact Metro or runtime error.