AdaptySDK-React-Native: Can not Archive iOS project
Project with react-native-adapty
integration can not be Archived to release and upload to the App Store.
I tested also with example app from this repo - the same result.
react-native-adapty=1.3.10
Build works, I can run it on the real device, but when trying to Archive in Xcode - getting the error:
Undefined symbols for architecture arm64:
"_swift_stdlib_isStackAllocationSafe", referenced from:
function signature specialization <Arg[1] = Owned To Guaranteed> of generic specialization <[Swift.String : Swift.String], [[Swift.String : Swift.String]]> of Swift._NativeSet.subtracting<A where A == A1.Element, A1: Swift.Sequence>(A1) -> Swift._NativeSet<A> in libAdapty.a(KinesisManager.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
It fails on the Linking stage
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18
Links to this issue
Commits related to this issue
- fix: (#20) fix_library_search_paths feature — committed to adaptyteam/AdaptySDK-React-Native by divanc 2 years ago
- fix: (#20) fix_library_search_paths — committed to adaptyteam/AdaptySDK-React-Native by divanc 2 years ago
- test: (#20) rn v0.67 — committed to adaptyteam/AdaptySDK-React-Native by divanc 2 years ago
Fixes found
@akolpakov
Problem is occurring after updating Xcode 13.3. I’ve tested these fixes on Adapty example, you can use any of listed:
1. Updating Library Search Paths in Xcode
You need to change Library Search Paths in Xcode:
"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)"
"$(SDKROOT)/usr/lib/swift"
Should work after that
2. Adding new
fix_library_search_paths
feature in your PodfileIn your podfile find
post_install
section and add one line offix_library_search_paths(installer)
there and function itself. Should work after that.Also, it is said, that updating RN to >= 0.67 helps, although I've failed to make this work with Adapty example
All of these fixes were found in this react-native-purchases issue. Huge props to them! If you are willing to find more info about this bug nature, it is also available there.
@akolpakov workaround found One of our users also faced this issue and has found a problem. They downgraded Xcode from 13.3 to 13.2 and everything worked.