Build fails on bitrise but works locally - ld: library not found for -lRNFetchBlob

Bitrise Build Issue Report template

Description of the issue

I have upgrade from react-native 0.44.3 to 0.50.0, I also use a library for caching images that was upgraded “react-native-cached-image”.

On bitrise build I get the error : (that blob is used for the above lib)
:x: ld: library not found for -lRNFetchBlob
:x: clang: error: linker command failed with exit code 1 (use -v to see invocation)

Everything works locally :

  • react-native run-ios :ok:
  • Xcode build :ok:
  • re-cloned repo, install bitrise-cli locally and bitrise run primary :ok:

Environment: Xcode Archive & Export 2.3.7 (always latest)
Xcode: 9.1 (same version as local)

fails on Xcode Archive & Export…


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • If you have multiple different build configurations (workflows), does the issue affect all/more than one? : NO
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : when upgraded react-native and a library

Other stacks

Can it be reproduced by running the build locally with our CLI ( ), after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( )?
NO, locally everything works

Build log

Please attach the build log (you can download the build log from the build’s page, once the build is finished, using the “Download log” button - floating at the bottom right corner of the log viewer), or if you can’t attach the whole log then send the full log through a private channel (e.g. email - ), with a link to the related Discuss issue.

enabled bitrise support for :
build log:

Hi @tibs,

Thanks for the #issues:build-issues report! :slight_smile:

Can you please follow this local debugging guide How to debug your build locally / "It works on my Mac/PC but not on" and let us know how it goes? Highlight: please do start with a clean git clone of the repository into a new directory, to prevent local caches / files which are not under version control.

Did you find a solution to this problem. I am also facing same issue just with a different library. I also upgraded from 0.44 to 0.51.

1 Like

@Evernym can you please follow the local debug guide (How to debug your build locally / “It works on my Mac/PC but not on”) and if that wouldn’t help create a new #issues:build-issues report? It’d help a lot to be able to help ASAP! :slight_smile: