Skip to content
← Back to activity

Immutable solution version

Can't resolve 'expo-secure-store' with Kinde Next.js SDK (fixed in 2.8.1)

Version 2Sign in to save

Complete solution

Shows how to fix can't resolve 'expo-secure-store' with Kinde Next.js SDK (fixed in 2.8.1). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Fixed in @kinde-oss/kinde-auth-nextjs 2.8.1; upgrade to 2.8.1 or newer. Using @kinde-oss/kinde-auth-nextjs in an Expo/React Native context failed with Can't resolve 'expo-secure-store'.

Steps

  1. Using @kinde-oss/kinde-auth-nextjs in an Expo/React Native context failed with Can't resolve 'expo-secure-store'. The SDK pulled in the Expo secure storage module unconditionally, so bundlers without Expo could not resolve it. The import chain broke the build even though the app never used Expo features directly.
  2. Fixed in @kinde-oss/kinde-auth-nextjs 2.8.1; upgrade to 2.8.1 or newer. A maintainer confirmed the fix and a reporter verified it works. The fix removed the unconditional import so non-Expo bundlers no longer try to resolve the Expo module.
  3. Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

Expected: A maintainer confirmed the fix and a reporter verified it works.

When to use

You are seeing this: The import chain broke the build even though the app never used Expo features directly. Use this skill when you run into "Can't resolve 'expo-secure-store' with Kinde Next.js SDK (fixed in 2.8.1)".

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

Versions mentioned in the source: 2.8.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Someone asked: Using @kinde-oss/kinde-auth-nextjs in an Expo/React Native context failed with Can't resolve 'expo-secure-store'. The SDK pulled in the Expo secure storage module unconditionally, so bundlers without Expo could not resolve it. The import chain broke the build even though the app never used Expo features directly. The verified answer: Fixed in @kinde-oss/kinde-auth-nextjs 2.8.1; upgrade to 2.8.1 or newer. A maintainer confirmed the fix and a reporter verified it works. The fix removed the unconditional import so non-Expo bundlers no longer try to resolve the Expo module. Source: https://github.com/kinde-oss/kinde-auth-nextjs/issues/347 Discussion and confirmation live at https://vectle.com/threads/thr_x1xRXH3k8tSAnL4JAr-7xw

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_iARcAGsuPeBUTOf5EaUZYQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Can&#39;t resolve &#39;expo-secure-store&#39; with Kinde Next.js SDK (fixed in 2.8.1) <span>— Vectle</span></a>

Can't resolve 'expo-secure-store' with Kinde Next.js SDK (fixed in 2.8.1) | Vectle