Hi I upgraded to v4.0.4. But it cause building failed.

Could you try cleaning in xcode and let me know if that fixes it? Thank you
I've added other troubleshooting steps here: https://github.com/DylanVann/react-native-fast-image/blob/master/docs/troubleshooting.md
I am experiencing the same. :\
ps: we'll go through the troubleshooting and see if everything gets fixed.
@edo1493 Have you tried those troubleshooting steps?
I've cleaned all the stale data I can think of and installed the new version on a new React Native project and it builds and works for me.
I'd like to be able to test on another machine to be 100% sure but I don't have one available at the moment. Also thinking about setting up some CI for this but all the iOS CI solutions cost money and I'm not sure yet which one would be best for this.
@DylanVann,
I did the following thing before building:
Got the same error as well, using pods is not an option for me.
Alright, I just got this error. Seems to only happen with release builds.
For now I'd suggest keeping the version fixed on the previous release until this is resolved and a new version is published. Sorry
So it seems like since FastImage is now supposed to use the version of FLAnimatedImage that SDWebImage compiles it needs to use:
#import <SDWebImage/FLAnimatedImageView.h>
Instead of:
#import <FLAnimatedImage/FLAnimatedImageView.h>
It's weird that it works in development mode with the second version but not in production mode.
Also if I do make that change without any other change I think that would break CocoaPods, so there should probably be some sort of conditional there. I'll need to look into it a bit more.
Apparently when running fastlane #import <SDWebImage/FLAnimatedImageView.h> doesn't work.
Yep, same issue here. Running in debug mode, but release throws same error. Tried all the steps as well (clearing cache, deleting modules/build folder, watchman del all, npm start reset cache, delete derived data in xcode, cmk shift k)
EDIT: same issue on 4.0.0 for release mode. Works fine in debug mode. Tried using both Xcode, as well as react-native-start in release.
Had to downgrade to 3.0.2
v4.0.6 is released. This issue should be fixed now.
Ended up doing it like this:
Seems to work in all the scenarios I tested:
Let me know if this fixes things, thank you
Most helpful comment
v4.0.6is released. This issue should be fixed now.Ended up doing it like this:
Seems to work in all the scenarios I tested:
Let me know if this fixes things, thank you