upgrade-support: Solution: Upgrading from 0.61.5 to 0.62.0 "Undefined symbol: _swift_getFunctionReplacement"

Following the SOLUTIONS in the topic works for me, just one thing:

Enable Dead Code Stripping --> This needed to be done for the TARGETS level, not PROJECT level

setting DEAD_CODE_STRIPPING to TRUE solved it for me 🙏

I managed to solve this issue just a few moments, ago. For me the problem was I entered the library search paths with quotes (") like so:

"$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)"

opposed to

$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)

and followed the rest of the guides in #13

@chestercharles ur solution in addition of

1- setting FB_SONARKIT_ENABLED=1

Go to Build Settings
Find Preprocessor Macros
To Debug add new value:
FB_SONARKIT_ENABLED=1

2- include /usr/lib/swift into Linking -> runpath search path , Also, for the record, after I built my app, it crashed on launch with Thread 1: signal SIGABRT Searching a bit deeper, I found this message: This copy of libswiftCore.dylib requires an OS version prior to 12.2.0. I added a File.swift in my projects, and it was ok. But if I removed the file again, it crashed again. So, in xCode, I went to BuildSettings -> Linking -> runpath search path , and manually changed each build line to:

/usr/lib/swift
$(inherited)

both those step with yours managed to make it work PS the above fixes where from other issue here and no credits goes to me

I did these steps from React Native 0.62 upgrade (Xcode) and set to project.pbxproj the following configs:

Change this:

IPHONEOS_DEPLOYMENT_TARGET = 9.0;

To this:

IPHONEOS_DEPLOYMENT_TARGET = 10.0;
LD_RUNPATH_SEARCH_PATHS = "/usr/lib/swift $(inherited)";
LIBRARY_SEARCH_PATHS = (
    "\"$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)\"",
    "\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"",
    "\"$(inherited)\"",
);

Remove DEAD_CODE_STRIPPING and add ENABLE_BITCODE = NO.

And it worked fine! 🚀

I am facing the same issue got these errors when build xcode

Undefined symbol: _swift_getFunctionReplacement
Undefined symbol: _swift_getOrigOfReplaceable

My xcode version is 12.1

None of those solutions works for me.

It works after I set “Don’t Dead Strip Inits and Terms” to “Yes”

Following the SOLUTIONS in the topic works for me, just one thing:

Enable Dead Code Stripping --> This needed to be done for the TARGETS level, not PROJECT level

This is very important. I had been setting on Project level and wasting my time. Thanks @ptgamr.

@AlexandrDobrovolskiy I had a problem where I set DEBUG macro to false after following https://github.com/react-native-community/upgrade-support/issues/25#issuecomment-608585271.

Go to Build Settings Find Preprocessor Macros To Debug add new value: FB_SONARKIT_ENABLED=1

If you’re like me and new to Xcode, this instruction might not be clear enough. Here’s a screenshot of the correct config:

The key is the $(inherited) so we don’t lose DEBUG=1 😃

After I implemented the solution, I kept getting the “No bundle url present” error. To fix it, I had to select my project -> select Build Settings -> Deployment (iOS) -> Strip Debug Symbols during Copy -> Set Debug to Yes. The reason is that in AppDelegate.m you have this piece of code:

#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif

In my case, since DEBUG was false, React Native was looking for a main.jsbundle file. After I set Debug to “Yes”, the error disappeared and my app ran without any issues.

I followed both the OP instructions and I’ve added FB_SONARKIT and LD_RUNPATH_SEARCH_PATHS AND it worked 🎉

Then I dug into the changes and realised that we don’t need the dummy file, it just looks that way because when you add it, it sets Always Embed Swift Standard Libraries to YES, and when you remove it, it sets it to NO 😁 So you can delete it, just revert the 2 lines that relate to Always Embed... OR re-added them as the OP did in step 4 - the same goes for FB_SONARKIT_ENABLED , which should be added automatically, but sometimes isn’t 😁

The rest of the changes are needed, as described in Setting up Flipper for iOS and Troubleshooting - since these are listed under setting up Flipper, I think they must be added to the original guide since I don’t see how anything can work if you don’t do them 😁 @pvinis?

Edit: I didn’t notice I was getting a warning:

[!] The `MadbarzMobileApp [Release]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-MadbarzMobileApp/Pods-MadbarzMobileApp.release.xcconfig'. This can lead to problems with the CocoaPods installation

but managed to fix it.

I have updated the react-native version 0.61.5 to 0.63.3 and I am also facing the below issue. Undefined symbol: _swift_getFunctionReplacement Undefined symbol: _swift_getOrigOfReplaceable

I tried the above solution but none of the solutions work for me.

Today I did something that I was hesitating a little bit but worked, I just created a new project and copy and paste everything from the old one, now it is working.

Instructions on how to manually add Flipper 0.62+ on Flipper site vs upgrade-support repo are pretty different. Check https://fbflipper.com/docs/getting-started/react-native-ios . Shouldn’t we point to Flipper site to follow react native instructions?

The troubleshooting page https://fbflipper.com/docs/troubleshooting/ covers most of the solutions mentioned here

I also had a few problems with android

Problem 1

What went wrong:
A problem occurred evaluating project ':react-native-webview'.
Could not initialize class org.jetbrains.kotlin.gradle.plugin.sources.DefaultKotlinSourceSetKt

Solution1

Upgrade react-native-webview per https://github.com/react-native-community/react-native-webview/issues/1011

Problem 2

error: cannot find symbol
        }catch (InvocationTargetException

This was coming from the initializeFlipper method in MainApplication.java.

Solution 2

Add this to MainApplication.java imports

import java.lang.reflect.InvocationTargetException;

This has been driving me crazy. I’ve lost track of the amount of things I’ve tried haha. A build setting in Xcode that got rid of these errors for me (giving way to entirely new errors instead… kill… me… ) was “Don’t Dead-Strip Inits and Terms”.

I also noticed that removing that second entry ($(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)) makes the project build without making any other changes.

I wonder if we really need that, because from the error message it sounds like it’s looking for _swift_getFunctionReplacement50 instead of _swift_getFunctionReplacement without 50 which I assume has to do with swift 5.

What will happen if we just omit that second file (since the project get’s built)? Any ideas?

After I implemented the solution, I kept getting the “No bundle url present” error. To fix it, I had to select my project -> select Build Settings -> Deployment (iOS) -> Strip Debug Symbols during Copy -> Set Debug to Yes. The reason is that in AppDelegate.m you have this piece of code:

#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif

In my case, since DEBUG was false, React Native was looking for a main.jsbundle file. After I set Debug to “Yes”, the error disappeared and my app ran without any issues.

Facing the same issue but Strip Debug Symbols During Copy didn’t help 😦