Undefined symbol: _OBJC_CLASS_$_RCTImageLoader #842

khasbilegt · 2021-03-04T04:46:24Z

Description

Build fails on react-native-screens versions 2.18.0, 2.18.1 but works fine on previous versions.

Screenshots

Steps To Reproduce

yarn upgrade react-native-screens@latest
yarn pod
xcode build

Expected behavior

Successful Xcode build

Actual behavior

Failed Xcode build

Package versions

React: v16.13.1
React Native: v0.63.4
React Native Screens: v2.18.1

WoLewicki · 2021-03-04T10:07:46Z

Can you reproduce this issue on the fresh react-native project? If no, it can be an issue of wrong transition between the react-native versions in your project. cc @jakmak24 since you had same problem.

jakmak24 · 2021-03-04T10:10:35Z

@khasbilegt Hi. I've experienced a similar issue and it was related to using use_frameworks! in Podfile.
Try adding the following step to your Podfile:

  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('RNScreens')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

kesha-antonov · 2021-03-05T10:28:28Z

pre_install do |installer|
installer.pod_targets.each do |pod|
if pod.name.eql?('RNScreens')
def pod.build_type
Pod::BuildType.static_library
end
end
end
end

thanks, it helped!

shariqsami · 2021-03-10T09:43:28Z

@jakmak24 its causing this error

ld: warning: directory not found for option '-L-L/Users/apple/apps/appElection/ios/Build/Products/Debug-iphonesimulator/RNScreens'
ld: library not found for -lRNScreens
clang: error: linker command failed with exit code 1 (use -v to see invocation)

phuchungnguyen78 · 2021-03-16T00:09:15Z

I got the same issue with @khasbilegt , try to add some codes as jakmak24's suggestion, but it doesn't work.
I created react native project with salesforce mobile SDK (https://developer.salesforce.com/docs/atlas.en-us.mobile_sdk.meta/mobile_sdk/react_native_new_project.htm)

d4niells · 2021-03-16T21:13:21Z

Does anyone know how to explain why this happens? I'm doing the integration of react native with the existing ios app and I'm having this same problem in the x86_64 architecture not only in lib react-native-screens but also in react-native-masked-view and react-native-svg

xcode: 12.4v
react-native: 0.63.4v

gmapnl · 2021-03-17T15:12:40Z

Exactly same issue, pre_install not helps

tried to add s.static_framework = true in RNScreens.podspec instead, without success.

Xcode : 12.4
React: v17.0.1
React Native: v0.64.0
React Native Screens: v2.18.1

sujith-surendranath · 2021-03-17T16:40:34Z

@phuchungnguyen78 did you find any solution for salesforce SDK + RN projects?

WoLewicki · 2021-03-17T16:43:15Z

If the change suggested by @jakmak24 doesn't work for you, you can always revert the commit that introduces this change: #768 with e.g. patch-package.

Jalil-Irfan · 2021-03-23T05:30:08Z

@khasbilegt Hi. I've experienced a similar issue and it was related to using use_frameworks! in Podfile.
Try adding the following step to your Podfile:
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('RNScreens')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

Thanks it helped me by pass the issue but I would like to know the actual fix and also I would like to know what issues i can expect in future because of this pod file change

sunzhongliangde · 2021-03-23T09:30:23Z

Sorry, I don't have this problem. Is there anyone else? Is there any problem using this version in a new project?

flash76 · 2021-03-28T13:13:55Z

Sorry, I don't have this problem. Is there anyone else? Is there any problem using this version in a new project?

@sunzhongliangde I'm using it in my project, and adding the pre install action to build RNScreens as a static library causes
Cycle inside FBReactNativeSpec; building could produce unreliable results. This usually can be resolved by moving the shell script phase '[CP-User] Generate Specs' so that it runs before the build phase that depends on its outputs.

gmapnl · 2021-04-02T14:02:03Z

Sorry, I don't have this problem. Is there anyone else? Is there any problem using this version in a new project?

@sunzhongliangde I'm using it in my project, and adding the pre install action to build RNScreens as a static library causes
Cycle inside FBReactNativeSpec; building could produce unreliable results. This usually can be resolved by moving the shell script phase '[CP-User] Generate Specs' so that it runs before the build phase that depends on its outputs.

It's another problem. Fixed for me with :

post_install do |installer|
  react_native_post_install(installer)
  
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
    end
    
    if (target.name&.eql?('FBReactNativeSpec'))
      target.build_phases.each do |build_phase|
        if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
          target.build_phases.move(build_phase, 0)
        end
      end
    end
  end
end

WoLewicki · 2021-04-07T11:13:36Z

I will close this issue since it is not react-native-screens specific and the solutions are already listed. Please comment here if something is wrong and we can reopen it then.

flash76 · 2021-04-11T01:32:03Z

@khasbilegt Hi. I've experienced a similar issue and it was related to using use_frameworks! in Podfile.
Try adding the following step to your Podfile:
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('RNScreens')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

I was also having this issue and I think I was able to fix it a bit more elegantly. Instead of doing use_frameworks! and putting pre-install directives, I used CocoaPods User-Defined Build Types and added :build_type => :dynamic_framework to the dependencies that required use_frameworks!.

billnbell · 2021-04-12T21:00:18Z

Sorry, I don't have this problem. Is there anyone else? Is there any problem using this version in a new project?

@sunzhongliangde I'm using it in my project, and adding the pre install action to build RNScreens as a static library causes
Cycle inside FBReactNativeSpec; building could produce unreliable results. This usually can be resolved by moving the shell script phase '[CP-User] Generate Specs' so that it runs before the build phase that depends on its outputs.

It's another problem. Fixed for me with :
post_install do |installer|
  react_native_post_install(installer)
  
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
    end
    
    if (target.name&.eql?('FBReactNativeSpec'))
      target.build_phases.each do |build_phase|
        if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
          target.build_phases.move(build_phase, 0)
        end
      end
    end
  end
end

I am using

target 'TheClub' do
  config = use_native_modules!

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => true
  )

  target 'TheClubTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable these next few lines.

  if !ENV['CI']
    use_flipper!({ 'Flipper' => '0.79.1' })

    post_install do |installer|
      flipper_post_install(installer)
      installer.pods_project.targets.each do |t|
        t.build_configurations.each do |config|
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
        end
      end
    end
  end
end

How do I fix it?

louishwh · 2021-04-28T06:09:25Z

post_install do |installer|

react_native_post_install(installer)

installer.pod_targets.each do |pod|
  if pod.name.eql?('RNScreens')
    def pod.build_type
      Pod::BuildType.static_library
    end
  end

  if pod.name.eql?('RNCMaskedView')
    def pod.build_type
      Pod::BuildType.static_library
    end
  end
end

installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '10.0'
        config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
    end
    
    if (target.name&.eql?('FBReactNativeSpec'))
         target.build_phases.each do |build_phase|
        if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
            target.build_phases.move(build_phase, 0)
        end
      end
    end
end

end

markwilcox · 2021-05-11T15:36:15Z

I've just run into this issue today after upgrading react-native-screens. I'm working on a complex hybrid native/react-native app with use_frameworks!. I've seen similar issues on other React Native modules with native code too. It's a question of build timing luck, because RNScreens.podspec has a missing dependency. Adding a new pod, or updating a pod can cause this to start failing, or be magically fixed again. The RNScreens pod is trying to be linked before the React-RCTImage pod has been compiled, hence the missing symbol at link time.

When everyone shifted from depending on 'React' to 'React-Core' because Xcode got fussy about that, some packages that depend on bits of React Native outside 'React-Core' have not added all those frameworks explicitly.

Form me adding:
s.dependency "React-RCTImage"
to RNScreens.podspec fixes this issue. Although it would be worth double-checking what classes from React Native are actually used and which modules they're in to make sure all the dependencies are captured, because otherwise it's just luck what gets built in what order in each project.

I hope that all makes sense and it would be great if this could be fixed in a future release @WoLewicki 🙏 - then I can remove my package patch.

WoLewicki · 2021-05-12T08:06:07Z

@markwilcox so could you make a PR with such a change and link it here for people to be able to test it and say if it resolves their issue? It would be great if we could resolve this issue by it.

markwilcox · 2021-05-12T11:12:52Z

I double checked the dependencies and it was only "React-RCTImage" that was missing. This gets our build through CI without any of the messy local podfile hacks suggested above. Made a PR - linked above. It shouldn't have any effect on users that don't have the error, you're just declaring your dependency on something that would get built anyway to ensure the correct build order.

LPitonakova · 2021-06-08T21:23:02Z

I've applied the suggested dependency "React-RCTImage" fix but keep getting the same error. Is there anything else you did, @markwilcox ? Did you also apply the pre-install instructions from above and if so, where exactly?

markwilcox · 2021-06-08T21:30:17Z

No pre-install hacks required @LPitonakova but you do need to pod install again after applying the fix.

You can check the dependency has been correctly added in your Pods project in Xcode afterwards.

LPitonakova · 2021-06-08T21:40:45Z

@markwilcox I did pod install, then cleaned and re-built the project as well. Still the same error. I feel like I'm missing something! When you say "You can check the dependency has been correctly added in your Pods project in Xcode afterwards." - how exactly would I do that please?

markwilcox · 2021-06-08T21:44:10Z

I’m on a phone, or I’d send you a screenshot. There should be a project called Pods in your Xcode Workspace. Inside that there is a target for each native module, and if you select react-native-screens then you should be able to see the dependencies.

LPitonakova · 2021-06-14T23:13:06Z

Hi @markwilcox sorry I don't see that & after trying a few other things, the error still persists. Here is a screenshot of the Pods -> RNScreens

My full pod file, of the project is:

platform :ios, '10.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'dopplleHarness' do
  # Pods for dopplleHarness
  pod 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
  pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
  pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
  pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/'
  pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
  pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-Core/RCTWebSocket', :path => '../node_modules/react-native/'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'ReactCommon/jscallinvoker', :path => "../node_modules/react-native/ReactCommon"
  pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
  pod 'Yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  use_native_modules!
  
  post_install do |installer|
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO'
      end
    end
  end
end




target 'dopplleShare' do
  
  
  use_modular_headers!
  use_native_modules!
  #inherit! :search_paths
  # Manually link packages here to keep your extension bundle size minimal
end

def find_and_replace(dir, findstr, replacestr)
  Dir[dir].each do |name|
      text = File.read(name)
      replace = text.gsub(findstr,replacestr)
      if text != replace
          puts "Fix: " + name
          File.open(name, "w") { |file| file.puts replace }
          STDOUT.flush
      end
  end
  Dir[dir + '*/'].each(&method(:find_and_replace))
end

markwilcox · 2021-06-15T10:43:01Z

Looking at your linked issue @LPitonakova I think you've gone wrong having use_native_modules! in the share extension target in the first place. The share extension should be all native, no React Native. Extension memory restrictions on iOS make React Native quite unusable inside them. Double check the build instructions for the share extension because I think it shouldn't be including anything at all via Cocoapods.

LPitonakova · 2021-06-15T18:43:15Z

Thanks for having a look at that @markwilcox the thing is though, If I take out the use_native_modules! for the share extension target, pods don't install because

[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `react-native-receive-sharing-intent` depends upon `React-Core`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

The share extension uses a react native library called react-native-receive-sharing-intent. I even tried the suggestion in the error message, so in my podfile I did:

target 'dopplleShare' do
  use_modular_headers!
end

But the error I get is the same. I am quite lost in this - are you able to see what I am doing wrong? Another weird things is that before XCode 12, I had another project that used the exact same share extension setup, with the use_native_modules! included for the share extension target. That project used to build all ok, even though I cannot build that project anymore either with XCode 12.

suzTheCoder · 2021-08-11T05:41:54Z

I have just commented #use_frameworks!
cd ios && pod install
and it worked for me.

ChiragALogicalloop · 2022-10-07T12:14:19Z

Sorry, I don't have this problem. Is there anyone else? Is there any problem using this version in a new project?

@sunzhongliangde I'm using it in my project, and adding the pre install action to build RNScreens as a static library causes
Cycle inside FBReactNativeSpec; building could produce unreliable results. This usually can be resolved by moving the shell script phase '[CP-User] Generate Specs' so that it runs before the build phase that depends on its outputs.

It's another problem. Fixed for me with :
post_install do |installer|
  react_native_post_install(installer)
  
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
    end
    
    if (target.name&.eql?('FBReactNativeSpec'))
      target.build_phases.each do |build_phase|
        if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
          target.build_phases.move(build_phase, 0)
        end
      end
    end
  end
end

It's working for me.
Thanks***

Biplovkumar · 2023-10-26T15:40:12Z

@khasbilegt Hi. I've experienced a similar issue and it was related to using use_frameworks! in Podfile.
Try adding the following step to your Podfile:
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('RNScreens')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end
Thanks it helped me by pass the issue but I would like to know the actual fix and also I would like to know what issues i can expect in future because of this pod file change

It worked. But It is not a good solution.

yashaRO mentioned this issue Mar 22, 2021

Can't build ios project after running forcereact create forcedotcom/SalesforceMobileSDK-Templates#310

Closed

Jalil-Irfan mentioned this issue Mar 23, 2021

Undefined symbols for architecture x86_64 : "_OBJC_CLASS_$_RCTImageLoader" bamlab/react-native-image-resizer#216

Closed

esilverberg mentioned this issue Apr 2, 2021

When upgrading to 0.64-rc3, error: Cycle in dependencies between targets 'FBReactNativeSpec' facebook/react-native#31034

Closed

WoLewicki closed this as completed Apr 7, 2021

WoLewicki mentioned this issue Apr 13, 2021

Build fails on iOS - Undefined symbols for architecture #887

Closed

markwilcox mentioned this issue May 12, 2021

Add missing dependency on React-RCTImage pod. #934

Merged

9 tasks

wmathurin mentioned this issue May 13, 2021

Fixes for compilation errors of RN template on xcode 12 forcedotcom/SalesforceMobileSDK-Templates#314

Merged

LPitonakova mentioned this issue Jun 14, 2021

Xcode 12 unable to link after adding the Share extension: _OBJC_CLASS_$_RCTImageLoader ajith-ab/react-native-receive-sharing-intent#78

Closed

0xnm mentioned this issue Aug 4, 2021

Upgrade bridges DataDog/dd-sdk-reactnative#94

Merged

c-basso mentioned this issue Jun 24, 2022

iOS Build Error - Link RNPDF (arm64) rumax/react-native-PDFView#221

Closed

gdpr1504 mentioned this issue Jan 23, 2023

[Firebase_messaging ] Error with IOS build related to RNFirebase Messaging invertase/react-native-firebase#6854

Closed

NicolasD27 mentioned this issue Apr 17, 2024

build framework Undefined symbols for architecture arm64 ,"facebook::jsc::makeJSCRuntime()", referenced from: software-mansion/react-native-reanimated#4254

Open

KingAmo mentioned this issue May 29, 2024

iOS build faied: ld: Undefined symbols software-mansion/react-native-reanimated#6062

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Undefined symbol: _OBJC_CLASS_$_RCTImageLoader #842

Undefined symbol: _OBJC_CLASS_$_RCTImageLoader #842

khasbilegt commented Mar 4, 2021

WoLewicki commented Mar 4, 2021

jakmak24 commented Mar 4, 2021 •

edited

Loading

kesha-antonov commented Mar 5, 2021

shariqsami commented Mar 10, 2021

phuchungnguyen78 commented Mar 16, 2021 •

edited

Loading

d4niells commented Mar 16, 2021 •

edited

Loading

gmapnl commented Mar 17, 2021 •

edited

Loading

sujith-surendranath commented Mar 17, 2021

WoLewicki commented Mar 17, 2021

Jalil-Irfan commented Mar 23, 2021

sunzhongliangde commented Mar 23, 2021

flash76 commented Mar 28, 2021

gmapnl commented Apr 2, 2021 •

edited

Loading

WoLewicki commented Apr 7, 2021

flash76 commented Apr 11, 2021

billnbell commented Apr 12, 2021

louishwh commented Apr 28, 2021

markwilcox commented May 11, 2021

WoLewicki commented May 12, 2021

markwilcox commented May 12, 2021 •

edited

Loading

LPitonakova commented Jun 8, 2021

markwilcox commented Jun 8, 2021

LPitonakova commented Jun 8, 2021

markwilcox commented Jun 8, 2021

LPitonakova commented Jun 14, 2021

markwilcox commented Jun 15, 2021

LPitonakova commented Jun 15, 2021

suzTheCoder commented Aug 11, 2021

ChiragALogicalloop commented Oct 7, 2022

Biplovkumar commented Oct 26, 2023

Undefined symbol: _OBJC_CLASS_$_RCTImageLoader #842

Undefined symbol: _OBJC_CLASS_$_RCTImageLoader #842

Comments

khasbilegt commented Mar 4, 2021

Description

Screenshots

Steps To Reproduce

Expected behavior

Actual behavior

Package versions

WoLewicki commented Mar 4, 2021

jakmak24 commented Mar 4, 2021 • edited Loading

kesha-antonov commented Mar 5, 2021

shariqsami commented Mar 10, 2021

phuchungnguyen78 commented Mar 16, 2021 • edited Loading

d4niells commented Mar 16, 2021 • edited Loading

gmapnl commented Mar 17, 2021 • edited Loading

sujith-surendranath commented Mar 17, 2021

WoLewicki commented Mar 17, 2021

Jalil-Irfan commented Mar 23, 2021

sunzhongliangde commented Mar 23, 2021

flash76 commented Mar 28, 2021

gmapnl commented Apr 2, 2021 • edited Loading

WoLewicki commented Apr 7, 2021

flash76 commented Apr 11, 2021

billnbell commented Apr 12, 2021

louishwh commented Apr 28, 2021

markwilcox commented May 11, 2021

WoLewicki commented May 12, 2021

markwilcox commented May 12, 2021 • edited Loading

LPitonakova commented Jun 8, 2021

markwilcox commented Jun 8, 2021

LPitonakova commented Jun 8, 2021

markwilcox commented Jun 8, 2021

LPitonakova commented Jun 14, 2021

markwilcox commented Jun 15, 2021

LPitonakova commented Jun 15, 2021

suzTheCoder commented Aug 11, 2021

ChiragALogicalloop commented Oct 7, 2022

Biplovkumar commented Oct 26, 2023

jakmak24 commented Mar 4, 2021 •

edited

Loading

phuchungnguyen78 commented Mar 16, 2021 •

edited

Loading

d4niells commented Mar 16, 2021 •

edited

Loading

gmapnl commented Mar 17, 2021 •

edited

Loading

gmapnl commented Apr 2, 2021 •

edited

Loading

markwilcox commented May 12, 2021 •

edited

Loading