Archiving with different build configuraton - "framework not found QBImagePicker for architecture armv7"

[tobycox]

Version

Tell us which versions you are using:

• react-native-image-crop-picker v0.11.2
• react-native v0.39

Platform

• iOS
• Android

Expected behaviour

Can build and Archive the project in an alternate build configuration.

Actual behaviour

Linker error:

ld: framework not found QBImagePicker for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Steps to reproduce

1. Project with separate build configurations. We have a Release-Staging build configuration which is a clone of our Release build configuration but with a different bundle ID and plist.

2. A Release-Staging scheme that archives using this build configuration.

3. Build and Archive using this scheme.

Has anyone run in to a similar issue? Seems like maybe the QBImagePicker framework isn't ending up in right build directory (Release instead of Release-Staging).

[mizinin]

have same issue with custom config schemes(

[tobycox]

@mizinin Have you had any luck getting around it? It's making me sad 😢

[deno028]

Getting the same issue. Can anybody solve it?

[tobycox]

Still getting this issue. Have tried using the cocoapods method as well as the manual embedding method but neither work.

[tobycox]

So I was right in that the frameworks aren't ending up in the right directory. I'm not sure how to actually fix this in a nice way, but I got around it by adding a Run Script phase to my project before "Compile Sources" which copies the frameworks over in to the correct directory so they can be found for linking.

if [ "${CONFIGURATION}" = "Release-Staging" ]; then
    cp -R "${BUILT_PRODUCTS_DIR}/../Release-iphoneos/QBImagePicker.framework" "${BUILT_PRODUCTS_DIR}"
    cp -R "${BUILT_PRODUCTS_DIR}/../Release-iphoneos/RSKImageCropper.framework" "${BUILT_PRODUCTS_DIR}"
fi

Replace "Release-Staging" with the name of your custom build configuration.

[richardgill]

For me I think the problem was really just related to: facebook/react-native#11813

I fixed using the library: https://github.com/Thinkmill/react-native-schemes-manager

[ivpusic]

this is the current react-native limitation.

As a workaround, follow facebook/react-native#11813 (comment).

After that, create another "User defined setting", name it for example: REACT_FRAMEWORKS_PATH, set value $(BUILD_DIR)/Release-$(PLATFORM_NAME), and then in "framework search paths" add $(REACT_FRAMEWORKS_PATH)

[ptgamr]

Adding to "Linked Frameworks And Libraries" like bellow fixed the problem for me:

Notice that QBImagePicker.framework is not in the list.

The irony is, if I added QBImagePicker.framework, the build would failed.