This repository was archived by the owner on Jun 23, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 23, 2025. It is now read-only.
'superwall-react-native' is not linked #35
Description
› Using development build
Error: The package 'superwall-react-native' doesn't seem to be linked. Make sure:
- You have run 'pod install'
- You rebuilt the app after installing the package
- You are not using Expo Go
In React Native _layout.tsx page.
useEffect(() => {
const apiKey = process.env.SUPERWALL_API_KEY || ''
Superwall.configure(apiKey)
}, []);What could possibly be the reason I'm getting this error?
Activity
lil-j commentedon Jan 17, 2025
I'm getting this error too.
lil-j commentedon Jan 17, 2025
Update: I was able to fix it by updating my eas-cli!
sudo npm install -g eas-cliJonfr0 commentedon Jan 17, 2025
Yes, I fixed it as well, I created a new EAS build.
lil-j commentedon Jan 18, 2025
Actually, I keep getting the same error again. Any other tips for mitigating it @Jonfr0
Jonfr0 commentedon Jan 19, 2025
Try going to expo and in your project, delete your current build and make a new one.
small-cactus commentedon Jan 29, 2025
I have the same issue, building locally with expo doesn't work, building using cloud with eas doesn't work, running prebuild and deleting and reinstalling everything doesn't work.
Installing the expo only version or the npm version doesn't matter, both don't work. I get a linking issue every time even though I am using the development build, and not the Expo Go version.
Does anybody have any fixes at all? I think I've tried every possible solution by now, it's gotta be a superwall problem.
Jonfr0 commentedon Jan 29, 2025
Haver you ran
npx expo-doctor?small-cactus commentedon Jan 29, 2025
Yes it did not fix the issue, my app wouldn't work unless I used version 1.2.2
Jonfr0 commentedon Jan 29, 2025
Do you know if it's a dependency issue or a version issue? Mine was related the
easbuildsmall-cactus commentedon Jan 30, 2025
I'm guessing it was a dependency issue, my app has worked on version 1.2.2 before. I never checked though