-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maximum call stack size exceeded when running react-native link #12188
Comments
When running
Same with any other package. |
The culprit is the 'xcode' package. It fails parsing my project at line 10 of file Adding a better error message would be nice. Here is the stacktrace :
|
Just ran into this issue as well. How did you figure out the callstack? |
I've got this one as well React Native 0.40.0, OSX 10.12.3. |
I went in the file and logged the error's stack ;) |
In case anybody else runs into this kind of error, ended up being my own fault. Creative insertion of console.log()'s into |
Thanks! Any tip on finding the duplicated entry? I'm considering going through my git history to find the breaking commit and then inspect it, but maybe you have a more efficient way of doing this? |
I used It would be nice to have file parser that helps with upgrading the Xcode project when upgrading React Native, that would at least tell if the |
I had duplicates in my |
I have removed the duplicates in my
And almost sure .pbxproj is at fault here, for a couple commits back, this works without any problem, but just not able to pinpoint the problem. PS : I come from a non-ios/xcode background |
My bad. Had duplicate image assets. Removing them and re-running helped. |
Letting Xcode Update the project settings fixed the issue for me. |
@cdesch Can confirm that this fixed it for me! For anyone wanting to know where you can update to the recommended settings: open xcode => the left sidebar should give you the option to update the recommended settings (it should have a yellow warning symbol next to it). |
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
Facing the same issue for lottie-react-native while linking. I am doing it for android. Any help is appreciated. |
Opened the old project for Android. I see the same error. Fixed in package.json |
SOLVED: Keeping this here if anyone else has the same issue. Having the same issue for react-native link react-native-svg. @cdesch / @jamesone's solution didn't work for me for this issue, though it did for a different maximum stack issue?
Solution: From linked above, this: Deleting "Recovered References: in xcode fixes the problem for me. |
Same issue, was able to fix it by deleting libRNFetchBlob.a from Recovered References. Works fine now. |
Description
What I did : I ran
react-native link
I expected the command to succeed, here was the output :
Reproduction
Haven't been able to reproduce yet (I can reproduce fine with my current repo, I just cannot create a broken project from a new project).
Solution
I've no idea.
Additional Information
The text was updated successfully, but these errors were encountered: