-
Notifications
You must be signed in to change notification settings - Fork 25.2k
How to ignore duplicate symbols error in a lib file? #29827
Copy link
Copy link
Closed
Labels
Needs: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: Environment InfoPlease run `react-native info` and edit your issue with that command's output.Please run `react-native info` and edit your issue with that command's output.Resolution: For Stack OverflowA question for Stack Overflow. Applying this label will cause issue to be closed.A question for Stack Overflow. Applying this label will cause issue to be closed.Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Metadata
Metadata
Assignees
Labels
Needs: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: Environment InfoPlease run `react-native info` and edit your issue with that command's output.Please run `react-native info` and edit your issue with that command's output.Resolution: For Stack OverflowA question for Stack Overflow. Applying this label will cause issue to be closed.A question for Stack Overflow. Applying this label will cause issue to be closed.Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Type
Fields
Give feedbackNo fields configured for issues without a type.
We are trying to integrating a
.astatic lib file into a React Native project. During build time, we encountered an error where a symbol (constant) is found declared multiple times in the single .a file.We also try to integrate it into a normal Xcode project while having largely the same build configuration. Xcode would only emit warnings about the duplicate symbols and the build was successful.
The screenshot below shows the linker flags we are using in the react-native project. Xcode would treat the warning as errors and will not allow the build to proceed. We suspect it was the inherited linker flags that came from other required react-native pods that cause this issue. Is there a way to ignore this error or to build them separately?
Environment