Unable to compile: Duplicate interface definition for class 'FLAnimatedImageView' #46

DerJacques · 2017-08-18T09:31:16Z

Hi there!

I'm having problems compiling my app after adding react-native-fast-image.

After running react-native link react-native-fast-image, I receive a bunch of duplicate interface definition for class 'FLAnimatedImageView' and property has a previous declaration errors.

Here's a subset of the errors I receive:

In file included from /Users/manuelthomsen/Coding/experiments/expo/woodn/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/SDWebImage/FLAnimatedImage/FLAnimatedImageView+WebCache.m:16:
In file included from /Users/manuelthomsen/Coding/experiments/expo/woodn/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/Vendors/FLAnimatedImage/FLAnimatedImage/FLAnimatedImage.h:13:
/Users/manuelthomsen/Coding/experiments/expo/woodn/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/Vendors/FLAnimatedImage/FLAnimatedImage/FLAnimatedImageView.h:22:1: error: duplicate interface definition for class 'FLAnimatedImageView'
@interface FLAnimatedImageView : UIImageView
^
In module 'FLAnimatedImage' imported from /Users/manuelthomsen/Coding/experiments/expo/test/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/SDWebImage/FLAnimatedImage/FLAnimatedImageView+WebCache.h:14:
/Users/manuelthomsen/Library/Developer/Xcode/DerivedData/test-ftzdxdyafvkexabeahltbammdnfq/Build/Products/Debug-iphonesimulator/FLAnimatedImage.framework/Headers/FLAnimatedImageView.h:22:12: note: previous definition is here
@interface FLAnimatedImageView : UIImageView
           ^
In file included from /Users/manuelthomsen/Coding/experiments/expo/test/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/SDWebImage/FLAnimatedImage/FLAnimatedImageView+WebCache.m:16:
In file included from /Users/manuelthomsen/Coding/experiments/expo/test/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/Vendors/FLAnimatedImage/FLAnimatedImage/FLAnimatedImage.h:13:
/Users/manuelthomsen/Coding/experiments/expo/test/node_modules/react-native-fast-image/ios/Vendor/SDWebImage/Vendors/FLAnimatedImage/FLAnimatedImage/FLAnimatedImageView.h:26:48: error: property has a previous declaration
@property (nonatomic, strong) FLAnimatedImage *animatedImage;

Any ideas on how to solve this?
This is a basic expo app that has just been detached.

Tested on RN v. 46 and 47.

Thank you!

The text was updated successfully, but these errors were encountered:

fredzhang · 2017-08-23T08:30:44Z

same problem here. please help

mortezaalizadeh · 2017-08-23T09:33:21Z

Same problem here :)

denny64 · 2017-08-28T03:16:17Z

+1

jacksontbryan · 2017-09-08T16:27:37Z

Blowing away the contents of my ios/build folder cleared this for me. The error only happened from react-native run-ios and wasn't reproducible from xcode directly.

srameshr · 2017-09-19T07:26:40Z

@jacksontbryan Did that. It did not solve the problem for me. It occurs when building for iPhone 5s and iOS version 9.0

MrLoh · 2017-09-21T13:00:23Z

I'm also encountering this issue. No idea how to fix it, or where it suddenly came form.

ruipaulo · 2017-09-21T13:30:55Z

Product-> Clean and then rm -rf ~/Library/Developer/Xcode/DerivedData/* did the trick for me.

i6mi6 · 2017-11-19T18:29:06Z

Cmd + Shift + K did it for me

jgbaEmento · 2017-12-05T07:46:39Z

same problem here ... cleaning and deleting derived data does not work here

kasran15 · 2017-12-17T21:38:47Z

Product -> Clean did the trick. Good suggestion!

pratt3351 · 2017-12-19T08:47:56Z

I’ve just delete project/ios/build folder and command react-native run-ios and it works fine!

bonlemuel · 2017-12-21T01:15:06Z

@rouge3351 Thanks for your solution. Saved me lots of time figuring it out. :)

luco · 2017-12-26T13:02:03Z

None of proposed fixes works for me.

MrLoh · 2017-12-26T15:31:48Z

@luco did you really try all three things?

rm -rf ~/Library/Developer/Xcode/DerivedData/*
rm -rf ios/build
in xcode Cmd + Shift + K

Did you try building from xcode and command line

@DylanVann is there any chance you could look into fixing this in the code. This is sucha a terrible annoyance for everyone using this library and it happens regularly. I have no idea what has to be setup in xcode to make this disappear, but there must be something, as I haven't gotten these errors from any other library.

luco · 2017-12-27T11:56:56Z

@MrLoh Apparently doing this steps the error went away.
I'll be monitoring this. Thanks a lot!

hoscarcito · 2018-02-09T10:00:20Z

This is really annoying indeed.
I'm subscribing for news!

broskoski · 2018-03-01T18:01:05Z

Same problem here. Running Project -> Clean and wiping the derived data folder did not work for me. If it helps at all, my project is set up with CocoaPods (though I manually linked the library in the build phases).

ruipaulo · 2018-03-01T19:54:50Z

@broskoski Did you do all the above suggested steps in @MrLoh 's last comment?

broskoski · 2018-03-01T19:55:31Z

@ruipaulo thanks, yes I did.

danmatthews · 2018-03-15T17:21:33Z

Also had this problem and couldn't solve it by performing all of the above steps.

I'm on a detached expo project, which means that i don't have an ios/build folder, so i couldn't do that one.

Had to uninstall as it was preventing me from building entirely.

DylanVann · 2018-03-18T12:14:00Z

node_modules (rm -rf node_modules then yarn)
watchman cache (watchman watch-del-all)
react-native packager cache (react-native start --reset-cache)
react native build (rm -rf ios/build)
xcode clean
xcode derived data

There are a lot of places things can get cached and mess things up when using React Native. Try clearing all those and I'm certain you won't have any more issues.

There's not really anything I could do to this library that would prevent these issues. I have dealt with these issues using many other libraries.

IMO React Native should have a clean command that handles all of these cases.

ruipaulo · 2018-03-21T15:47:57Z

@DylanVann I know, that it is probably super hard to find the bug that is causing this. On the other hand, it is happening consistently once or twice per week in our project. This is only and always caused by fast-image (we have also many other native libraries in the project). I know that there is probably no easy fix for this, but I think this issue should remain open as long as it is not fixed. Maybe at some point somebody might come up with a solution. This is a relevant bug, it is costing us at least an hour dev time per week and many users coming new to your library might spent hours trying to fix find a solution. This shouldn't be perceived as nagging, we love your library, but this is a relevant bug.

foggy1 · 2018-03-21T20:15:20Z

This happens in completely fresh build environments, e.g. when using continuous integration tools. It actually makes CI completely untenable with respect to iOS builds.

DannyAlb · 2018-03-22T11:53:25Z

I do not recommend doing this, but our extremely unacceptable and voodoo workaround was that after trying to build normally and getting above errors, to build the FastImage project separately, and add the library statically to the project (the libFastImage.a).

Unacceptable, voodoo, but the only way we got it to works :)

brenwell · 2018-04-06T07:17:35Z

I am wondering if the issue is caused because there is actually a duplicate?

Looks like its included twice.

I'm no xcode expert though

hoscarcito · 2018-04-07T03:34:20Z

As @foggy1 mention, this happens on fresh build environments, making it useless with CI tools.
@brenwell I saw the same but I don't understand how it works iOS nor why it works after cleaning the project.
Any light over here?

tomauty · 2018-04-18T16:42:01Z

@brenwell They are the same file. Not sure why it's included twice but if that could be resolved, all users here could finally check Parallelize Builds again...

oferRounds · 2018-04-19T13:50:07Z

+1

DylanVann · 2018-04-21T18:30:33Z

I'm looking into it a bit more. I have run into this.

I cannot replicate the issue on a new project though.

brenwell · 2018-04-21T22:23:01Z

The issue seems to come and go. Personally I find it easier to replicate via ‘react-native run-ios ‘ than via Xcode. Perhaps that helps

DylanVann · 2018-04-22T01:14:29Z

I made some changes to the FastImage project that might fix this.

Set deprecated ALWAYS_SEARCH_USER_PATHS to NO. (e7ba4a7)
Fix FLAnimatedImage header search path. (883dc06)
Remove FLAnimatedImage from FastImage project since it's already included in SDWebImage. Installation remains the same as before when using CocoaPods. (a2d9fe2)

The changes are published as v4.0.4. Please let me know wether or not you're still experiencing this issue after upgrading.

brenwell · 2018-04-22T06:03:33Z

Awesome. Will check thanks

VicFrolov · 2018-04-24T00:13:46Z

Getting same issue on version 4.0.4

Removed build folder, removed node modules, cleared watchman, installed node modules, npm reset cache, deleted all derived data. cleared xcode cache. Not sure what else to do :/

brenwell · 2018-04-24T08:44:33Z

I haven't seen the issue since I upgraded to 4.0.4 that doesn't mean it won't appear though

For anyone interested here is my clean all the things script

# react-native
    watchman watch-del-all
    rm -rf node_modules && npm install
    rm -rf $TMPDIR/haste-map-react-native-packager-*
    rm -rf $TMPDIR/react-native-packager-cache-*
    rm -rf $TMPDIR/metro-bundler-cache-*

# xcode
    xcodebuild -project ios/vs2.xcodeproj -configuration Release clean
    xcodebuild -project ios/vs2.xcodeproj -configuration Debug clean
    rm -rf ~/Library/Developer/Xcode/DerivedData
    rm -f /ios/build

 # cocoapods
    pod deintegrate --project-directory=./ios/
    rm -rf ./ios/Pods
    pod install --project-directory=./ios/

DylanVann · 2018-04-25T07:25:12Z

There were some issues with v4.0.4, they should be resolved in the latest version (v4.0.6). See: #189

Ingibjorg · 2018-04-26T00:10:30Z

Thanks @DylanVann . This solved the issue for me 🙏

schlaegerz · 2018-05-03T17:25:58Z

I am on 4.0.8 and still getting this issue

DylanVann · 2018-05-04T03:14:16Z

You will probably still have this issue immediately after you upgrade to v4.0.8.

Do a clean build (xcode clean / rm -rf ios/build). I haven't seen this issue again since doing that.

luco · 2018-07-25T21:11:33Z

OK, I got this issue again and solved by doing a xcode clean and removing ios/build folder.

duro · 2018-09-25T21:38:49Z

@DylanVann we are seeing this on latest version of react-native-fast-image with React 0.57. Not sure if 0.57 has anything to do with it. The biggest problem is that we use CI to build our releases, which always start from a clean state. We are consistently getting the issue with every build.

One thing we have noticed is that another one of our dependencies, the Braze/Appboy SDK, also depends on SDWebImage.

Has any further light been shed on this issue? We are going crazy trying to make any progress on resolving this.

dmkmedina · 2018-10-04T10:25:46Z

@duro Did you find a way to resolve this with the braze/appboy sdk? we're also having a similar issue

duro · 2018-10-04T19:59:51Z

@dmkmedina: Pinging @theonetheycallneo as he was the one on our team who got it sorted out. I'll be honest, it wasn't straightforward.

onurzorluer · 2018-10-09T11:35:58Z

Xcode 10 has a new build system. I had same problem in Xcode 10. I found that switching to the Legacy Build Systems solved the problem.
To switch to the legacy build system do the following:

File -> Project/Workspace Settings...
Under Build System choose: Legacy Build System

theonetheycallneo · 2018-10-12T17:59:45Z

@dmkmedina Our solution wasn't ideal, but we forked the react-native-fast-image and stripped out their SDWebImage.framework, then had their iOS project inherit from our parent umbrella iOS project:
https://github.com/FreebirdRides/react-native-fast-image/commits/master

We then manually linked our parent iOS project to SDWebImage with Appboy's latest bundled release of SDWebImage.

Basically, we been manually linking frameworks on our umbrella, then we fork any conflicting libs and have them correctly inherit from the parent.

Hope that helps shed some light.

bnap00 · 2018-11-10T06:33:21Z

Currently, I am on

"react-native-firebase": "^5.1.0",

and I am facing

/node_modules/react-native-fast-image/ios/FastImage/FFFastImageView.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

atereshkov · 2019-02-28T21:53:48Z

Flutter:
Just press Cmd + Shift + K in Xcode and then rebuild it.

tonygentilcore mentioned this issue Nov 30, 2017

v2.0.1: iOS build failed #95

Closed

MrLoh mentioned this issue Dec 12, 2017

Encounter error when running command react-native run-ios #102

Closed

gianpaj mentioned this issue Dec 18, 2017

Error compiling on iOS11.2 #112

Closed

DylanVann closed this as completed Mar 18, 2018

MrLoh mentioned this issue May 17, 2018

Apple Mach-O Linker Error Group #206

Open

dheerajsarwaiya mentioned this issue May 9, 2020

Not Working with iOS miguelpruivo/flutter_file_picker#270

Closed

alburdette619 mentioned this issue Sep 8, 2021

reapplied clear image cache PR #818

Closed

Unable to compile: Duplicate interface definition for class 'FLAnimatedImageView' #46

Unable to compile: Duplicate interface definition for class 'FLAnimatedImageView' #46

Comments

DerJacques commented Aug 18, 2017

fredzhang commented Aug 23, 2017

mortezaalizadeh commented Aug 23, 2017

denny64 commented Aug 28, 2017

jacksontbryan commented Sep 8, 2017

srameshr commented Sep 19, 2017

MrLoh commented Sep 21, 2017

ruipaulo commented Sep 21, 2017 • edited Loading

i6mi6 commented Nov 19, 2017 • edited Loading

jgbaEmento commented Dec 5, 2017

kasran15 commented Dec 17, 2017

pratt3351 commented Dec 19, 2017

bonlemuel commented Dec 21, 2017 • edited Loading

luco commented Dec 26, 2017

MrLoh commented Dec 26, 2017

luco commented Dec 27, 2017 • edited Loading

hoscarcito commented Feb 9, 2018

broskoski commented Mar 1, 2018 • edited Loading

ruipaulo commented Mar 1, 2018

broskoski commented Mar 1, 2018

danmatthews commented Mar 15, 2018

DylanVann commented Mar 18, 2018 • edited Loading

ruipaulo commented Mar 21, 2018

foggy1 commented Mar 21, 2018

DannyAlb commented Mar 22, 2018 • edited Loading

brenwell commented Apr 6, 2018

hoscarcito commented Apr 7, 2018

tomauty commented Apr 18, 2018

oferRounds commented Apr 19, 2018

DylanVann commented Apr 21, 2018

brenwell commented Apr 21, 2018

DylanVann commented Apr 22, 2018 • edited Loading

brenwell commented Apr 22, 2018

VicFrolov commented Apr 24, 2018

brenwell commented Apr 24, 2018

DylanVann commented Apr 25, 2018

Ingibjorg commented Apr 26, 2018

schlaegerz commented May 3, 2018

DylanVann commented May 4, 2018

luco commented Jul 25, 2018

duro commented Sep 25, 2018

dmkmedina commented Oct 4, 2018

duro commented Oct 4, 2018

onurzorluer commented Oct 9, 2018

theonetheycallneo commented Oct 12, 2018

bnap00 commented Nov 10, 2018

atereshkov commented Feb 28, 2019

ruipaulo commented Sep 21, 2017 •

edited

Loading

i6mi6 commented Nov 19, 2017 •

edited

Loading

bonlemuel commented Dec 21, 2017 •

edited

Loading

luco commented Dec 27, 2017 •

edited

Loading

broskoski commented Mar 1, 2018 •

edited

Loading

DylanVann commented Mar 18, 2018 •

edited

Loading

DannyAlb commented Mar 22, 2018 •

edited

Loading

DylanVann commented Apr 22, 2018 •

edited

Loading