-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failed with error '_swift_getTypeByMangledNameInContextInMetadataState' when adding Notification Content Extension to iOS project. #29246
Comments
Same here, but when trying to implement Apollo for Graphql as a swift package |
|
how to resolve? |
I use the following method to solve the problem LIBRARY_SEARCH_PATHS = (
"\"$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)\"",
- "\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"",
+ "\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.2/$(PLATFORM_NAME)\"",
"\"$(inherited)\"",
); |
@hengkx cool, now it builds 😃 |
I also had this issue and asked about it on the Swift forums. The cause is trying to link against an older Swift runtime while targeting a newer version of the OS. You should be able to just remove those As mentioned in the above Swift forums thread:
|
@hengkx, it works for me! Thanks a lot! |
Sorry for commenting on a closed issue, but I'm still experiencing this problem and nothing seems to help. I've tried changing my EDIT: Fixed it! My notification service extension had a different deployment target version than the RN app. |
Same issue here, adding a WidgetExtension to a blank react-native app causes this issue. None of the above fixes seem to work |
👆 This is the real fix |
@mcoevert true. I just remove those |
Thank You! This solved it! Holy S@#%! |
Works well! Thank you 🙏 |
Description
Build failed with an error when adding Notification Content Extension to iOS project.
React Native version:
react-native info result
Steps To Reproduce
Expected Results
Add Notification Content Extension to React Native project and build it successfully.
The text was updated successfully, but these errors were encountered: